Daz Studio 2026 Beta - version 6.25.2026.9715! (Updated April 09, 2026)

Richard Haseltine · February 20

Yui said:

How do I download this beta!? It doesn't show up in the DIM!

Click the Download Filters in ready to Download and make sure you have this version of DS, and the beta release channel, checked.

inquire · February 21

Tugpsx said:

nemesis10 said:

jbowler said:

The LOD script doesn't work on Alpha at all. I'm surprised that things are still being released that simply won't work on the next version. It's not that _all scripts don't work_; 3DU's pose controls (the ones to lock and unlock the parameters) work just fine. Good thing or I wouldn't be able to use the Alpha at all! Iray Light Manager Pro, which I always found very useful, does not work but it's fairly old and I've worked out how to do all the important stuff myself (though dealing with emissive surfaces is still a PITA, with or without the script.)

Most Scripts that are released will probably not work with the Alpha; that is kind of the point of being an Alpha i.e. to get a working proof of concept rather than a finished product for people to write scripts for. Hence, the scripts work perfectly fine in the general release and Beta. I would be if people were writing scripts for such an early work in progress.

If the scripts are first edited in DS6 and then encrypted in DS4 they will work in both versions. Some scripts created in DS6 or DS4 and encrypted in DS6 will not work in DS4 due to the change in encryption schema.
Some unencrypted scripts work great in both versions, but to distribute them they should be in DES format which causes them to no longer work in DS4 if DS6 is the encrypter.

I thought the scripts had to be completely rewritten. Are you saying that there's an easier process?

inquire · February 21

Tugpsx said:

nemesis10 said:

jbowler said:

The LOD script doesn't work on Alpha at all. I'm surprised that things are still being released that simply won't work on the next version. It's not that _all scripts don't work_; 3DU's pose controls (the ones to lock and unlock the parameters) work just fine. Good thing or I wouldn't be able to use the Alpha at all! Iray Light Manager Pro, which I always found very useful, does not work but it's fairly old and I've worked out how to do all the important stuff myself (though dealing with emissive surfaces is still a PITA, with or without the script.)

Most Scripts that are released will probably not work with the Alpha; that is kind of the point of being an Alpha i.e. to get a working proof of concept rather than a finished product for people to write scripts for. Hence, the scripts work perfectly fine in the general release and Beta. I would be if people were writing scripts for such an early work in progress.

If the scripts are first edited in DS6 and then encrypted in DS4 they will work in both versions. Some scripts created in DS6 or DS4 and encrypted in DS6 will not work in DS4 due to the change in encryption schema.
Some unencrypted scripts work great in both versions, but to distribute them they should be in DES format which causes them to no longer work in DS4 if DS6 is the encrypter.

I thought the scripts had to be completely rewritten. Are you saying that there's an easier process?

Richard Haseltine · February 21

inquire said:

Tugpsx said:

nemesis10 said:

jbowler said:

The LOD script doesn't work on Alpha at all. I'm surprised that things are still being released that simply won't work on the next version. It's not that _all scripts don't work_; 3DU's pose controls (the ones to lock and unlock the parameters) work just fine. Good thing or I wouldn't be able to use the Alpha at all! Iray Light Manager Pro, which I always found very useful, does not work but it's fairly old and I've worked out how to do all the important stuff myself (though dealing with emissive surfaces is still a PITA, with or without the script.)

Most Scripts that are released will probably not work with the Alpha; that is kind of the point of being an Alpha i.e. to get a working proof of concept rather than a finished product for people to write scripts for. Hence, the scripts work perfectly fine in the general release and Beta. I would be if people were writing scripts for such an early work in progress.

If the scripts are first edited in DS6 and then encrypted in DS4 they will work in both versions. Some scripts created in DS6 or DS4 and encrypted in DS6 will not work in DS4 due to the change in encryption schema.
Some unencrypted scripts work great in both versions, but to distribute them they should be in DES format which causes them to no longer work in DS4 if DS6 is the encrypter.

I thought the scripts had to be completely rewritten. Are you saying that there's an easier process?

It's plug-ns that definitely fail, scripts are more variable. Some scripts may require extensive reworking, some will work as-is.

weder482 · February 21

Dear DAZ Studio Team,

I have been a long-time member of the DAZ 3D community, and until recently I had no significant issues with rendering in DAZ Studio. However, after upgrading my graphics card to an NVIDIA RTX 5060 Ti (16GB), I began experiencing serious problems specifically with GPU rendering of large scenes.

Smaller scenes render correctly without issues when both CPU and GPU are enabled. However, when I attempt to render larger scenes (10 or more characters, full environments, detailed assets, complex lighting setups), one of two things happens:

The render outputs a completely black image, or
DAZ Studio throws an error and shuts down.

Interestingly, when I switch the render settings to CPU-only, these large scenes do render successfully, although the process takes an extremely long time and causes significant system overheating.

I purchased the RTX 5060 Ti with 16GB of VRAM specifically to handle larger, more complex scenes in Iray. At the moment, however, GPU rendering of such scenes appears unusable in DAZ Studio, which is quite disappointing given the purpose of the upgrade.

For context, I actively use other 3D applications such as Blender and Substance Painter, and I do not encounter similar GPU-related rendering failures there.

I would appreciate clarification on the following points:

Is the RTX 5000 series fully supported in the current alpha/beta version of DAZ Studio?
Are there known compatibility or driver issues affecting GPU rendering with this card?
Are there recommended settings or configuration changes to enable stable GPU rendering of large scenes?
Are there any plans to expand rendering engine support beyond NVIDIA Iray in the future?

I am willing to provide full system specifications and log files if needed to help diagnose the issue.

Thank you in advance for your assistance.

Best regards,Dear DAZ Studio Team,

I have been a long-time member of the DAZ 3D community, and until recently I had no significant issues with rendering in DAZ Studio. However, after upgrading my graphics card to an NVIDIA RTX 5060 Ti (16GB), I began experiencing serious problems specifically with GPU rendering of large scenes.

Smaller scenes render correctly without issues when both CPU and GPU are enabled. However, when I attempt to render larger scenes (10 or more characters, full environments, detailed assets, complex lighting setups), one of two things happens:

The render outputs a completely black image, or
DAZ Studio throws an error and shuts down.

Interestingly, when I switch the render settings to CPU-only, these large scenes do render successfully, although the process takes an extremely long time and causes significant system overheating.

I purchased the RTX 5060 Ti with 16GB of VRAM specifically to handle larger, more complex scenes in Iray. At the moment, however, GPU rendering of such scenes appears unusable in DAZ Studio, which is quite disappointing given the purpose of the upgrade.

For context, I actively use other 3D applications such as Blender and Substance Painter, and I do not encounter similar GPU-related rendering failures there.

I would appreciate clarification on the following points:

Is the RTX 5000 series fully supported in the current alpha/beta version of DAZ Studio?
Are there known compatibility or driver issues affecting GPU rendering with this card?
Are there recommended settings or configuration changes to enable stable GPU rendering of large scenes?
Are there any plans to expand rendering engine support beyond NVIDIA Iray in the future?

I am willing to provide full system specifications and log files if needed to help diagnose the issue.

Thank you in advance for your assistance.

Best regards.

weder482 · February 21

and I would also like to ask what about plugins from older versions of daz3D and older props? Namely, this prop cannot be used in the current version. https://www.daz3d.com/mdbd-blood-n-dirt--geoshell-manager

Azure Thessian · February 21

I have one question on ergonomics UI front.

Is there any chance we can get back Colorized General Tab in DAZ6 (&4.24)? I mean transforms X (Red), Y(Green), Z (Blue) and same for Rotation and Scale.

I regret massively upgrading to 4.24 a while back. It's highly disorientating, I so often pick the wrong axis it's not even funny.

For now staying away from DAZ6. I tested it few months ago on Mac and it was in general OK, it amazingly fast imported e.g. 1.5M poly TIE-Interceptor model I've, until tried to do render preview which immediately crashed the program. Also as I read this thread a lot of plug-ins won't work (probably permanently). Nope. In general for now sticking to my good old 3090 because 5000 series is just one horror story after another, with no stable version of DAZ6 I don't even go further. Will jump to 6090 or a Mac if Metal gets full API-IRAY render support-translation.

felis · February 21

Azure Thessian said:

I have one question on ergonomics UI front.

Is there any chance we can get back Colorized General Tab in DAZ6 (&4.24)? I mean transforms X (Red), Y(Green), Z (Blue) and same for Rotation and Scale.

For changing axis colors go to Windows > Style > Customize > 5. 3D axis

IN DS 4.x you could Alt-click on the colors and they reset to default, but that doesn't seem to be the case in DS 6.x

Richard Haseltine · February 21

weder482 said:

Dear DAZ Studio Team,

I have been a long-time member of the DAZ 3D community, and until recently I had no significant issues with rendering in DAZ Studio. However, after upgrading my graphics card to an NVIDIA RTX 5060 Ti (16GB), I began experiencing serious problems specifically with GPU rendering of large scenes.

Smaller scenes render correctly without issues when both CPU and GPU are enabled. However, when I attempt to render larger scenes (10 or more characters, full environments, detailed assets, complex lighting setups), one of two things happens:

The render outputs a completely black image, or

DAZ Studio throws an error and shuts down.

Interestingly, when I switch the render settings to CPU-only, these large scenes do render successfully, although the process takes an extremely long time and causes significant system overheating.

I purchased the RTX 5060 Ti with 16GB of VRAM specifically to handle larger, more complex scenes in Iray. At the moment, however, GPU rendering of such scenes appears unusable in DAZ Studio, which is quite disappointing given the purpose of the upgrade.

For context, I actively use other 3D applications such as Blender and Substance Painter, and I do not encounter similar GPU-related rendering failures there.

I would appreciate clarification on the following points:

Is the RTX 5000 series fully supported in the current alpha/beta version of DAZ Studio?

Are there known compatibility or driver issues affecting GPU rendering with this card?

Are there recommended settings or configuration changes to enable stable GPU rendering of large scenes?

Are there any plans to expand rendering engine support beyond NVIDIA Iray in the future?

I am willing to provide full system specifications and log files if needed to help diagnose the issue.

Thank you in advance for your assistance.

Best regards,Dear DAZ Studio Team,

I have been a long-time member of the DAZ 3D community, and until recently I had no significant issues with rendering in DAZ Studio. However, after upgrading my graphics card to an NVIDIA RTX 5060 Ti (16GB), I began experiencing serious problems specifically with GPU rendering of large scenes.

Smaller scenes render correctly without issues when both CPU and GPU are enabled. However, when I attempt to render larger scenes (10 or more characters, full environments, detailed assets, complex lighting setups), one of two things happens:

The render outputs a completely black image, or

DAZ Studio throws an error and shuts down.

Interestingly, when I switch the render settings to CPU-only, these large scenes do render successfully, although the process takes an extremely long time and causes significant system overheating.

I purchased the RTX 5060 Ti with 16GB of VRAM specifically to handle larger, more complex scenes in Iray. At the moment, however, GPU rendering of such scenes appears unusable in DAZ Studio, which is quite disappointing given the purpose of the upgrade.

For context, I actively use other 3D applications such as Blender and Substance Painter, and I do not encounter similar GPU-related rendering failures there.

I would appreciate clarification on the following points:

Is the RTX 5000 series fully supported in the current alpha/beta version of DAZ Studio?

Are there known compatibility or driver issues affecting GPU rendering with this card?

Are there recommended settings or configuration changes to enable stable GPU rendering of large scenes?

Are there any plans to expand rendering engine support beyond NVIDIA Iray in the future?

I am willing to provide full system specifications and log files if needed to help diagnose the issue.

Thank you in advance for your assistance.

Best regards.

Which driver are you using? Please post your log file for a session in which you had this problem.

Leana · February 21

weder482 said:

and I would also like to ask what about plugins from older versions of daz3D and older props? Namely, this prop cannot be used in the current version. https://www.daz3d.com/mdbd-blood-n-dirt--geoshell-manager

Plugins made for DS4 won't work at all in DS2026, they all would need an updated version: at least be recompiled to use the DS2026 SDK, but more work might be needed depending on what the plugin does and whether the features and functions it used were modified in DS2026.

The product you linked is made of a bunch of scripts. Unlike plugins, scripts made for DS4 are not fundamentally incompatible with DS2026. Some scripts will work as is, but the changes to the script engine and SDK mean that some will require an update to work in DS2026.

heraclexss · February 22

Hello everyone, does anyone know if the render queue works in beta version 2026? I have the script, but it does not appear in the beta version.

Richard Haseltine · February 22

heraclexss said:

Hello everyone, does anyone know if the render queue works in beta version 2026? I have the script, but it does not appear in the beta version.

The Premier version does, yes.

jrlamar · February 22

Running an Intel Core Ultra 9 285K with 64GB of RAM and a 5070 Ti with 16GB of VRAM on Windows 11 Pro and NVIDIA Studio Driver 591.74, and this "Beta" consistently locks up and crashes my system if I try to render anything above 4K resolution. Not only does it lock it up, but when it reboots, one of my monitor's color profiles is also mysteriously reset. Bizarre and terrible performance.

weder482 · February 22

Hello,

I am experiencing a recurring crash loop with Daz Studio 6 Public Build (2026). The application starts to load but crashes and closes immediately.

Workaround used:
I have to manually delete the Studio6 and Studio6 Public Build folders in %appdata%\Roaming\DAZ 3D to get the program to launch. However, this is only a temporary fix and the issue returns shortly after.

Log File:
I have attached my log.txt file to this message. I hope it helps you identify which plugin or component is triggering the crash.

https://drive.google.com/file/d/1gdl4p0UjWsRAWRmNMQ6fQ5JlpXk-npwy/view?usp=sharing

Thank you for your assistance in resolving this.

Best regards,

weder482 · February 22

Dear Support / Development Team,

I am writing to report a critical issue encountered during high-load rendering tasks in DAZ Studio. While I am impressed with the capabilities of the latest version, I have consistently experienced a full system reboot when processing specific high-fidelity scenes.

Scenario Description:
The issue occurs during the rendering phase of a scene containing:

Characters: 10 Genesis 9 figures in HD quality.
Assets: Full clothing sets utilizing 4K texture maps.
Engine: NVIDIA Iray (GPU Accelerated).

Observed Behavior:
In previous versions, a VRAM overflow typically resulted in an application crash or a fallback to a black screen. However, in the current environment, the system performs a hard restart shortly after the render begins. This suggests a potential critical conflict between the Iray engine, the display driver, and the hardware power management under extreme load.

System Specifications:

Intel(R) Core(TM) Ultra 7 265K (3.90 GHz), GPU nvidia RTX 5060 TI 16GB ,RAM 64,0 GB, Windows 11 Home,
NVIDIA Driver Version: 591.74
DAZ Studio Version: Daz studio 2026 (6:25) Public Beta

Attached Logs:
For your review, I have provided the DAZ Studio Log File (Help > Troubleshooting > View Log File) and the Windows Event Viewer summary.

https://drive.google.com/file/d/1Jq7sgKLNnOivJ-Em4GZy45rIZqbQAl57/view?usp=sharing

I would appreciate any insights into whether this is a known limitation or if there are specific optimization settings you would recommend for handling such high-density scenes.

Thank you for your time and for your continuous work on improving DAZ Studio.

Best regards,

weder482 · February 22

jrlamar said:

Running an Intel Core Ultra 9 285K with 64GB of RAM and a 5070 Ti with 16GB of VRAM on Windows 11 Pro and NVIDIA Studio Driver 591.74, and this "Beta" consistently locks up and crashes my system if I try to render anything above 4K resolution. Not only does it lock it up, but when it reboots, one of my monitor's color profiles is also mysteriously reset. Bizarre and terrible performance.

I agree, it happens to us too!

Richard Haseltine · February 22

These crashes do sound like a driver or even hardware issue - have you tried rolling back to a driver closer to the minimum required version? 576.80 is the oldest Studio driver supported according to the Iray thread.

Masterstroke · February 22

Masterstroke said:

Hard to reproduce:
Occasionally, the latest ALPHA shows the wrong material in preview and final render, although listed correctly in the material parameter list.

first: DS 4.24
second: DS ALPHA 6.25

Still a thing. No improvements, still the same issue with the 2026 BETA.

alex.schead · February 22

Hey everyone!
I've been using the Alpha 2025 now Beta 2026 version for a while now because of my GPU.
Specs:
Intel i7-14700K
32GB RAM
5070ti 16GB VRAM

I don't really have an choice, but for me it's actually been better than expected to use the Alpha version. I have been patiently hoping for it to get better because there are obvious problems, but it's useable and for me it's been mostly a learning experience so... I'm just glad I had the option.
Anyway, the only thing I wanted to ask about to see if we have any predictions of when it could improve is the saving/loading of sets/personas/characters/scenes with accuracy. If building on the same scene there are no issues, but when trying to save characters, for example, to be loaded as either of those things in a different scene, they never load as saved. The morphs "break", as in, the character just doesn't have the same apperance so I assume it's just not the right dials being loaded?
I imagine it's something the team is aware but I was hoping to know if it would be address sooner rather than later.
Has anyone else noticed this too?
Thanks, and keep up the good work!

weder482 · February 23

Richard Haseltine said:

These crashes do sound like a driver or even hardware issue - have you tried rolling back to a driver closer to the minimum required version? 576.80 is the oldest Studio driver supported according to the Iray thread.

YES I TRIED THAT AND SAME RESULT.

weder482 · February 23

alex.schead said:

Hey everyone!
I've been using the Alpha 2025 now Beta 2026 version for a while now because of my GPU.
Specs:
Intel i7-14700K
32GB RAM
5070ti 16GB VRAM

I don't really have an choice, but for me it's actually been better than expected to use the Alpha version. I have been patiently hoping for it to get better because there are obvious problems, but it's useable and for me it's been mostly a learning experience so... I'm just glad I had the option.
Anyway, the only thing I wanted to ask about to see if we have any predictions of when it could improve is the saving/loading of sets/personas/characters/scenes with accuracy. If building on the same scene there are no issues, but when trying to save characters, for example, to be loaded as either of those things in a different scene, they never load as saved. The morphs "break", as in, the character just doesn't have the same apperance so I assume it's just not the right dials being loaded?
I imagine it's something the team is aware but I was hoping to know if it would be address sooner rather than later.
Has anyone else noticed this too?
Thanks, and keep up the good work!

Do you have any photos/screenshots?

alex.schead · February 23

weder482 said:

alex.schead said:

Hey everyone!
I've been using the Alpha 2025 now Beta 2026 version for a while now because of my GPU.
Specs:
Intel i7-14700K
32GB RAM
5070ti 16GB VRAM

I don't really have an choice, but for me it's actually been better than expected to use the Alpha version. I have been patiently hoping for it to get better because there are obvious problems, but it's useable and for me it's been mostly a learning experience so... I'm just glad I had the option.
Anyway, the only thing I wanted to ask about to see if we have any predictions of when it could improve is the saving/loading of sets/personas/characters/scenes with accuracy. If building on the same scene there are no issues, but when trying to save characters, for example, to be loaded as either of those things in a different scene, they never load as saved. The morphs "break", as in, the character just doesn't have the same apperance so I assume it's just not the right dials being loaded?
I imagine it's something the team is aware but I was hoping to know if it would be address sooner rather than later.
Has anyone else noticed this too?
Thanks, and keep up the good work!

Do you have any photos/screenshots?

Sure, I can post some. What would help more?
Rendered versions of the same lips for example to show in the original scene and then when imported into a different one?

johndoe_36eb90b0 · February 24

Anyone running on Windows 11 and Windows 10 make sure you have the absolute latest driver from NVIDIA and that you installed February 10 (KB5077181 for Win11, KB5075912 for Win10) patch -- latest January patches introduced instability for NVIDIA users.

Know that latest driivers have open issues (for example RTX Video Super-Resolution showing black screen in browsers and media players using DXVA path) -- should be fixed in next one.

johndoe_36eb90b0 · February 24

@Richard

Here is a list of outstanding issues I am having in latest beta:

Slideshow when moving figures around the scene

Easy to reproduce:
- Open DAZ Studio
- Set viewport to Iray preview
- Set object resolution to 1/1 for manipulation
- Load single G8 or G9 figure
- Pan camera left / right and note latency
- Now move figure left / right by dragging X transform slider and note latency
Expected behavior:
- Since both movements are relative to each other (you either move camera or the figure) the latency should be the same
Actual behavior:
- Pan is smooth, figure movement is slideshow to the point of being unusable and having to switch to textured mode to pose things
Notes:
- I understand that moving a figure vs moving a camera is different (figure movement includes changes to scene graph), but it wasn't this bad in 4.x version -- especially not with single figure and empty scene on high-end hardware.

Broken encrypted (DSE) scripts

Easy to reproduce:
- Open Daz Studio
- Load a G8 figure
- Load a 3rd party geograft
- Load a script to copy textures from figure to geograft
Expected behavior:
- Script works
Actual behavior:
- Script fails with error because API has been changed and compatibility was broken
Notes:
- I understand the necessity of updating SDK API, what I have a problem with is that vendors whose products I bought refuse to update the scripts because the SDK API is supposedly still not stable and they might as well never update it depending on whether they still offer support for specific products. Daz should find a way to enable us to still run those scripts in v6 because having to load a scene in 4.24 just to apply a different material preset every time you need to change something defeats the purpose of having new Daz Studio version. If the scripts were not encrypted we could fix them ourselves with some effort but with encryption that is impossible. Daz could at least provide a DSE migration tool that decrypts, updates, and re-encrypts those scripts because I am sure that material copy script could be fixed up automatically.

dForce Simulation not updating preview while in Iray mode

Easy to reproduce:
- Open Daz Studio
- Load a figure
- Load dForce hair or cloth
- Set viewport to Iray preview
- Hit Simulate
Expected result:
- dForce object simulation is shown
Actual result:
- Viewport drops from Iray to something resembling smooth shaded
- Figure (and its movement if Start Bones From Memorized Pose is enabled) is visible
- dForce object simulated is invisible
- If the dForce object is selected only the bounding box is moving in viewport while simulating
Notes:
- I am not expecting dForce to actually render in Iray mode, but whatever mode the viewport drops into while simulating should show the object being simulated. Having to switch viewport to textured or smooth shaderd to see what's going on during simulation is inconvenient.

So much from me for now, hope you can pass this to devs.

Richard Haseltine · February 26

johndoe_36eb90b0 said:

@Richard

Here is a list of outstanding issues I am having in latest beta:

Slideshow when moving figures around the scene

Easy to reproduce:
- Open DAZ Studio
- Set viewport to Iray preview
- Set object resolution to 1/1 for manipulation
- Load single G8 or G9 figure
- Pan camera left / right and note latency
- Now move figure left / right by dragging X transform slider and note latency
Expected behavior:
- Since both movements are relative to each other (you either move camera or the figure) the latency should be the same
Actual behavior:
- Pan is smooth, figure movement is slideshow to the point of being unusable and having to switch to textured mode to pose things
Notes:
- I understand that moving a figure vs moving a camera is different (figure movement includes changes to scene graph), but it wasn't this bad in 4.x version -- especially not with single figure and empty scene on high-end hardware.

I don't see any great difference (but I am using a 5090). As you say, there is some lag as the actual 3D data is being updated as opposed to a movement of the viewpoint.

Broken encrypted (DSE) scripts

Easy to reproduce:
- Open Daz Studio
- Load a G8 figure
- Load a 3rd party geograft
- Load a script to copy textures from figure to geograft
Expected behavior:
- Script works
Actual behavior:
- Script fails with error because API has been changed and compatibility was broken
Notes:
- I understand the necessity of updating SDK API, what I have a problem with is that vendors whose products I bought refuse to update the scripts because the SDK API is supposedly still not stable and they might as well never update it depending on whether they still offer support for specific products. Daz should find a way to enable us to still run those scripts in v6 because having to load a scene in 4.24 just to apply a different material preset every time you need to change something defeats the purpose of having new Daz Studio version. If the scripts were not encrypted we could fix them ourselves with some effort but with encryption that is impossible. Daz could at least provide a DSE migration tool that decrypts, updates, and re-encrypts those scripts because I am sure that material copy script could be fixed up automatically.

Scripts depend on the Qt version to an extent, there are chnages thata re outside Daz' control (though they have been able to implement workarounds in some cases). Whether a script works or not depends on exactly which features it uses, how it is written, and whether it risked using undocumented features.

dForce Simulation not updating preview while in Iray mode

Easy to reproduce:
- Open Daz Studio
- Load a figure
- Load dForce hair or cloth
- Set viewport to Iray preview
- Hit Simulate
Expected result:
- dForce object simulation is shown
Actual result:
- Viewport drops from Iray to something resembling smooth shaded
- Figure (and its movement if Start Bones From Memorized Pose is enabled) is visible
- dForce object simulated is invisible
- If the dForce object is selected only the bounding box is moving in viewport while simulating
Notes:
- I am not expecting dForce to actually render in Iray mode, but whatever mode the viewport drops into while simulating should show the object being simulated. Having to switch viewport to textured or smooth shaderd to see what's going on during simulation is inconvenient.

The Viewport drops to OpenGL but it does update in my simple text case (just a dynamic plane). This may be a perfomance issue.

So much from me for now, hope you can pass this to devs.

comradenikola92 · February 26

Constant crashes on scene loads that work in 4.24, the level of ineptitude on display from these devs is beyond shocking. This wouldn't be okay for a free product, let alone with a fat subscription. No error output, just main window disappears and Progress window of loader keeps spinning.

Azure Thessian · February 26

felis said:

Azure Thessian said:

I have one question on ergonomics UI front.

Is there any chance we can get back Colorized General Tab in DAZ6 (&4.24)? I mean transforms X (Red), Y(Green), Z (Blue) and same for Rotation and Scale.

For changing axis colors go to Windows > Style > Customize > 5. 3D axis

IN DS 4.x you could Alt-click on the colors and they reset to default, but that doesn't seem to be the case in DS 6.x

Wherever you're Good Fellow I bow to you in eternal gratitude. Thank you so VERY much!

I struggled for so long in my glorified ignorance. ;)

Richard Haseltine · February 26

comradenikola92 said:

Constant crashes on scene loads that work in 4.24, the level of ineptitude on display from these devs is beyond shocking. This wouldn't be okay for a free product, let alone with a fat subscription. No error output, just main window disappears and Progress window of loader keeps spinning.

Which isn't happening for most people, so it is probably a local factor or factors rather than incompetence at the Daz end. Any scene? Even one with a cube primitive? if it is more selective are theer features or content common to the problem scenes? Can you, in a simple case (if there is one) recreate the scene in 2025, save it, and reload it successfully? Will it load in DS 4? Are the content diiectories the same in both versions, and listed in the same order?

strenif · February 26

As I'm sure many other have asked about it. Any word on Mesh Grabber being added in?

It's such a vital everyday tool, I'm kinda supprised DAZ devs have not added the function as a built in tool that comes with the software.

I'm currently in an odd spot where I've upgraded my PC to a RTX 5090 so I have to use 2026 Beta, so getting that function back tops my lists of things I'd like to see added in the next update.

Richard Haseltine · February 27

strenif said:

As I'm sure many other have asked about it. Any word on Mesh Grabber being added in?

It's such a vital everyday tool, I'm kinda supprised DAZ devs have not added the function as a built in tool that comes with the software.

I'm currently in an odd spot where I've upgraded my PC to a RTX 5090 so I have to use 2026 Beta, so getting that function back tops my lists of things I'd like to see added in the next update.

Geometry Sculptor is the current iteration of Mesh Grabber, and will import mesh Grabber modifiers from DS 4. That is the only update there will be. dForms with weight maps can do a lot of the same work, they are what II hae used in the past (never bought any of the actual Mesh Grabbers and I haven't yet made any real use of Geometry Sculptor).

Notifications

Daz Studio 2026 Beta - version 6.25.2026.9715! (Updated April 09, 2026)

Comments

How do I download this beta!? It doesn't show up in the DIM!

Adding to Cart…