Daz Studio 6.25[.0.x], General Release!

Leana

rokkr said:

Robert Freise said:

Really? With all the continuing troubles being posted in the Beta thread it was still acting like Alpha and not a Beta

Indeed... According to the logs (https://docs.daz3d.com/public/software/dazstudio/6/change_log), there's no Beta release. I guess we're the Alpha testers.

The log is not up to date then, as DS2026 has been in beta for quite some time.

edit: there's no title with "beta" in the log page, but the switch to beta is actually recorded in section about  build 6.25.2026.2920

 

DoctorJellybean

khorneV2 said:

ds6 with filament

The first screenshot shows a pointlight? Press Ctrl and L (or Window - Preview Lights)

khorneV2

DoctorJellybean said:

khorneV2 said:

ds6 with filament

The first screenshot shows a pointlight? Press Ctrl and L (or Window - Preview Lights)

i switched the preview lights with no luck

khorneV2

khorneV2 said:

DoctorJellybean said:

khorneV2 said:

ds6 with filament

The first screenshot shows a pointlight? Press Ctrl and L (or Window - Preview Lights)

i switched the preview lights with no luck

i reloaded the scene with the figure only with the same issue

vrba79

Hurdy3D said:

vrba79 said:

Can the AI be uninstalled? I don't want it. Period.

it's a plugin which can be disabled. was one of the first things I did

Okay. I can live with that!!

Robert Freise

Still acting like Alpha

theflarf

I get far more common crashes on random general viewport work with DS6 than DS4.24, just like the public alpha previously

So no improvement in the user experience for me, therefore no chance of using it as my regular tool. 

jmucchiello

khorneV2 said:

By the way is it possible to convert customactions.dsx from ds4.24 to ds 6?

Most of the scripts probably don't work. But in theory you should be able to just copy it from the one folder to the other as long as you haven't done anything else. Problem is you probably shouldnt't over write the menu or toolbar files that puts the customactions into the layout.

khorneV2

jmucchiello said:

khorneV2 said:

By the way is it possible to convert customactions.dsx from ds4.24 to ds 6?

Most of the scripts probably don't work. But in theory you should be able to just copy it from the one folder to the other as long as you haven't done anything else. Problem is you probably shouldnt't over write the menu or toolbar files that puts the customactions into the layout.

ouch !. i do not test ds5 preview. no script compatibility is a problem !

AndrewJJP

DoctorJellybean said:

AndrewJJP said:

yonashald said:

I already got the KB5089573 It didn't do anything for me.

If this is the one some people thoought was helpful, it's hard to see why.

https://support.microsoft.com/en-gb/topic/may-26-2026-kb5089573-os-builds-26200-8524-and-26100-8524-preview-f378c8ae-0170-47c9-a1e9-dfef978c8e17#id0ebdl=normal_rollout

This is about secure boot, inprovements to update delivery and AI. OK, there may well be some minor changes, but if anyone found this heled, then my guess (and this is based on long progessional experience) is thay changed something else at the same time without realising...

...I have also learned not to dismiss things without trying them, but I think this is so unlikely to help that I'm not going to try it early. If it works on the 9th, I will be pleasantly surprised. I would hope Daz is working on a fix, and given it's listed as a known issue, I'm sure they will be. No need to worry, just a little longer to wait IMO. I'll check back when the first point release is available. I cannot honestly see this being anything other than a Daz problem.

https://www.windowslatest.com/2026/05/28/windows-11-kb5089573-just-made-pcs-more-responsive-direct-download-links-msu/ ;

Ah, thank you. That is very helpful. I can see why people might point to that. If it fixes it, I will be happy. But I don't think it will.

Relying on a brand new OS feature to make something that used to work, work again, isn't really the right answer. I do not think any professional software engineer would believe that is a good answer, and neither do I think Daz is offering that as a solution. It's not how I read it anyway. I hope they are saying it's something might help people while they sort it out properly.

I say this partly because my 3090 did not need a low latency profile to move the iRay viewport smoothly, even with reasonably complex scenes. Also partly because my 5090 which has problems running DS6 does not need a low latency proifile to edit 4K HDR H.265 video, something it can do slightly faster than the 3090 can.

But the main reason I say it is that the low latency profile appears to work by allowing the CPU to run at a higher clock speed under some circumstances, so my immediate question was whether this is CPU-bound. No, not in my case. Not a single core is maxed out, they. They max out when I let go of the mouse and it catches up, but that is because it's rendering. It is the same story with the GPU. It doesn't start working until the viewport catches up. So basically, it's not doiing much, and that is why there is lag. I cannot see why making the CPU run more quickly is going to help if Daz isn't asking the CPU do do enough to max it out, and the KB doesn't even mention the GPU.

BUT, as I said, I will be very pleased if it does work, and these things are complicated. Maybe it will work and I don't care about being wrong it it makes Daz work again!

AndrewJJP

And I should also say some positives. I am really impressed with how quickly things load compared to before. It's a massive step torwards IMO. Once the teething troubles are ironed out, I'm really looking forward to getting back into things.

Saint

A positive I haven't seen mentioned (maybe I missed it) is the new "Adaptive Displacement" setting on Iray Uber. This generates polygons to support displacement and it's going to incredibly enhance the use of that moving forward.

A negative I must reiterate is these viewport problems. I'm highly dubious that a Windows update will resolve this. Microsoft is an easy scapegoat but maybe fix problems like these BEFORE launching your product?

omvendt

So, now DS works with RTX5090? How about dual RTX5090?

Is it still the case that the speed doubles with two GPUs but the video memory remains that of the single card?

 

kevphil

Viewport Lag?!? 

Are you kidding me? That's the single biggest concern I have had with ALL PREVIOUS versions! So, what else is new? I had really hoped the abominable slowness of the Viewport might finally be addressed... I guess not, :(

I was actually hoping for some direct implementation of Nvidia Omniverse, to maybe get DAZ closer speed-wise to what I can see in Character Creator.

Richard Haseltine

Masterstroke said:

DAZStudio 4 had an "Unistaller" folder, DAZStudio6 BETA and DAZ Studio 6 have not.
The DIM uninstall doesn't work and the Windows uninstaller doesn't work.
I would like a clean removal of DAZStudio 6, please.

So you installed through DIM and it isn't showing an uninstal option? Is it showing anything (that seems a very short list in the screenshot)? If it really isn't showing anything after trying to uninstall then you can simply delete the application folder (which will remove the plug-ins too, if you had installed them) though that is rather drastic and definitely a last resort.

Sorel

Funnily enough, I can't use Daz 6 for anything currently cause now I have to wait for the octane render plugin to be updated for this version. Maybe by the time that's done other plugins will be updated as well. I also really like the new texture shaded viewport. It is a bit choppy for me but nothing too bad. I suspect it will probably continue to be worked on.

Richard Haseltine

abelundercity_7fb40cbc22 said:

Iray preview works fine. Iray render dumps to a black screen. I am disgruntled.

What are your settings in Render Settings>Hardware? Have you tried a really simple scene, like a primitive?

brainmuffin

Leana said:

brainmuffin said:

How does one remove the Beta build version?

You should be able to uninstall it with DIM. 

I thought perhaps that, but it is not listed in the installed area, though it is listed under Advanced Settings -> Applications.

Richard Haseltine

jjb24 said:

Leana said:

jjb24 said:

Leana said:

jjb24 said:

DoctorJellybean said:

Elor said:

The name implies it should work with Daz Studio 4.24, but just to be sure: if I'm updating Default Ressources for Daz Studio 4.23+, it won't cause any problem with Daz Studio 4.24 ?

No. 

Is there any place that describes what 'Default Resources for Daz Studio 4.23+' is? What does it add? What does it remove? Why should I install it?

"Default resources" contains basic things you need to use DS like the default shaders and lights.

While I appreciate your reply it doesn't help much. I use 4.24 now so I must have the basic things you need to use it. I've also been using all the alpha and beta releases on the same PC because it has a 5090. If I install this file will DIM install it on Daz 4.24, Daz 6, or both? I will not install the released version of Daz 6 until I understand what will happen to 4.24. I understand expert users may appreciate the new features in Daz 6 but I'm not an expert and the two main things that matter to me are both bad. First most of my script based products and all of my plug-in products don't work in Daz 6 and I suspect some of them never will. Second, I spend almost all of my time in Daz using the main viewport and the performance of the main viewport in 4.24 is much, much better than it is in 6. Until both of these issues are addressed in Daz 6 I will continue using it only for rendering with my 5090. If necessary I will simply continue using the last beta and ignore the released version.

Nothing will happen to DS4.24 if you install DS6, they're separate installs and can be both installed on the same computer. You can then point DS6 to the same content directories as DS4 if you want.

The default resources files are content, not a part of the program. You install them into a DS content directory. If your DS6 uses the same content directories as DS4 then it should already have these files.

Thanks for the clarification. I have been sharing the content directory with both versions of Daz. If I understand correctly there is no need for me to install the 'Default Resources for Daz 4.23+' file since I already have this content from my installation of 4.24. Since this is the case I'll simply hide this file in DIM rather than installing it.

The package in DIM is an update, so you should probably install it (you might back up the current zip first if you are concerned - you could then reinstall that version by replacing the  new zip wiith the old in the DIM Downloads folder, then running DIM Offline to install).

Different question. I see people asking about uninstalling the beta. I guess this means that the Daz 6 release version will not update the beta installation and after installation I will have 3 versions of Daz on my PC: 4.24, 6 (2026) beta, and 6. Is there any problem with leaving all 3 versions on the machine other than wasting disk space?

Richard Haseltine

Tannim said:

DoctorJellybean said:

Lonesome Cowboy said:

I’ve gone ahead and installed it now, and I’ve also adjusted the directories. However, there is still something located in `C:\dokuemte` that I don't want there—and don't recognize. As described in the forum, I was able to copy over the `user_styles` and `user_layouts` files and largely restore my screen layout. So far, no serious issues have arisen, aside from the fact that the scripts, bookmarks, and similar items are no longer present in DS6. Although all the plugins appear "green" in the list, none of them are actually present or functional. The same applies to the toolbar at the top. Furthermore—despite having imported the saved layouts—one still has to manually set the screen background to white. In principle, using the software for actual work is not yet advisable.
But will there be content that only works in DS6? Then i would need a new content-folder

 What is in `C:\dokuemte`?

they are using an non english version of windows I imagine it's just documents C:\Documents and Settings

Even then, that would be the Windows XP path - I think it was WIndows 7 that switched to /Users/Documents/ - and XP is not supported. But I think the question was what files/folders were being placed there? 

Richard Haseltine

arne207 said:

Here's a bug: "Shift-Y" should open the symmetry tab but doesn't.

EDIT: It does work, but only after clicking on a limb - not when selecting the limb in the scene tab.

Focus seems to matter mor than it did in DS 4, but that isn't wholly a bad thing as it stops unwanted aplication of key-presses (e.g. people hated that using a key to jump to the first item starting with that letter in a content pane also triggered a Viewport move if Keyboard Navigaction was on)

Saint

Sorel said:

Funnily enough, I can't use Daz 6 for anything currently cause now I have to wait for the octane render plugin to be updated for this version. Maybe by the time that's done other plugins will be updated as well. I also really like the new texture shaded viewport. It is a bit choppy for me but nothing too bad. I suspect it will probably continue to be worked on.

It's closer to what you see in Blender, and I really like being able to toggle different textures by type. Gonna take some getting used to but the pros far outweigh the cons. Looking forward to enjoying it when Daz sorts out these viewport issues.

Richard Haseltine

khorneV2 said:

jmucchiello said:

khorneV2 said:

By the way is it possible to convert customactions.dsx from ds4.24 to ds 6?

Most of the scripts probably don't work. But in theory you should be able to just copy it from the one folder to the other as long as you haven't done anything else. Problem is you probably shouldnt't over write the menu or toolbar files that puts the customactions into the layout.

ouch !. i do not test ds5 preview. no script compatibility is a problem !

Whether or not scripts are compatible will vary - it is plug-ins that definitely won't be without a new version.

Richard Haseltine

omvendt said:

So, now DS works with RTX5090? How about dual RTX5090?

Is it still the case that the speed doubles with two GPUs but the video memory remains that of the single card

I'm not sure anyone  has tried, and I believe the new cards have chnaged the way that they communicate (no need for an nVlink widget) so depending on your system pooling memory for materials may be possible.

bluejaunte

Richard Haseltine said:

arne207 said:

Here's a bug: "Shift-Y" should open the symmetry tab but doesn't.

EDIT: It does work, but only after clicking on a limb - not when selecting the limb in the scene tab.

Focus seems to matter mor than it did in DS 4, but that isn't wholly a bad thing as it stops unwanted aplication of key-presses (e.g. people hated that using a key to jump to the first item starting with that letter in a content pane also triggered a Viewport move if Keyboard Navigaction was on)

It's wholly bad as far as I can tell. Shortcuts must work no matter what pane is active. If there's a special case, like the cursor is in some text field that people can type in, then Daz Studio needs to treat that as a special case and disable keyboard shortcuts then and there. Anything else is backwards.

Case in point, my Camera Manager plugin uses number keys to change to cameras quickly. If the plugin is in focus, or a viewport or the Content Library, it works fine.If the scene or parameters pane are active, it doesn't. There's no world where that is acceptable.

jmucchiello

bluejaunte said:

Richard Haseltine said:

arne207 said:

Here's a bug: "Shift-Y" should open the symmetry tab but doesn't.

EDIT: It does work, but only after clicking on a limb - not when selecting the limb in the scene tab.

Focus seems to matter mor than it did in DS 4, but that isn't wholly a bad thing as it stops unwanted aplication of key-presses (e.g. people hated that using a key to jump to the first item starting with that letter in a content pane also triggered a Viewport move if Keyboard Navigaction was on)

It's wholly bad as far as I can tell. Shortcuts must work no matter what pane is active. If there's a special case, like the cursor is in some text field that people can type in, then Daz Studio needs to treat that as a special case and disable keyboard shortcuts then and there. Anything else is backwards.

Case in point, my Camera Manager plugin uses number keys to change to cameras quickly. If the plugin is in focus, or a viewport or the Content Library, it works fine.If the scene or parameters pane are active, it doesn't. There's no world where that is acceptable.

So when you edit a parameter you want the camera to switch 3 times when you type 1 5 0?

bluejaunte

jmucchiello said:

bluejaunte said:

Richard Haseltine said:

arne207 said:

Here's a bug: "Shift-Y" should open the symmetry tab but doesn't.

EDIT: It does work, but only after clicking on a limb - not when selecting the limb in the scene tab.

Focus seems to matter mor than it did in DS 4, but that isn't wholly a bad thing as it stops unwanted aplication of key-presses (e.g. people hated that using a key to jump to the first item starting with that letter in a content pane also triggered a Viewport move if Keyboard Navigaction was on)

It's wholly bad as far as I can tell. Shortcuts must work no matter what pane is active. If there's a special case, like the cursor is in some text field that people can type in, then Daz Studio needs to treat that as a special case and disable keyboard shortcuts then and there. Anything else is backwards.

Case in point, my Camera Manager plugin uses number keys to change to cameras quickly. If the plugin is in focus, or a viewport or the Content Library, it works fine.If the scene or parameters pane are active, it doesn't. There's no world where that is acceptable.

So when you edit a parameter you want the camera to switch 3 times when you type 1 5 0?

Could swear I just mentioned that shortcuts need to be disabled when people are typing into textboxes? Which by the way works just fine in DS4. I never had an accidental camera change when typing stuff 

Ashcloud

Wedge said:

Unfortunately my very first experience with the new software made me go back to 4.24 instantly.

Why? 

My well-designed model (MSO Barbara) already equipped with a hair (dForce Practical Ponytail Hair) and a dress (Golden Order Dress) didn't load properly. The hair just did not show up. Works perfectly in 4.24 though. 

Edit -> My mistake.

Then I started a test-render in Daz 6 and the result came up much too bright and ugly. I am not eve sure why, but the details look horrible, the skin of the model looks bad. The default lighting (dome?) could be the reason.

But it's just a very bad experience to begin with, don't you think?

I mean, 4.24 works perfectly, so why would I step into a software that gives me such a bad experience from the very beginning?

And why is it so bad, anyway?

 

I had the same issue initially. Check the Geneal render settings in DAZ 6 and turn off Auto Headlamp.  

 

Ashcloud

The only issue that I have had so far is that I can't get Riversoft Arts Turbo Loader Manager for G9 to work in DAZ 6.

Also, a minor issue ...I don't really see the point of the Colour Node option in the Scene tab. Is there a way to remove that?

3Diva

I'm not going to read five pages of comments to find out if anyone else has this issue (I'm sorry, just don't have the time right now). But I just installed Daz Studio 6 and Iray Preview doesn't work at all. The character stays gray (it has textures and you can see the textures in other previews like texture shaded and Filament), it's a Genesis 9 character. Iray preview doesn't work at all. I have a 5070 Ti if that helps. It also doesn't load the Environment and Tone mapping nodes when I switch to Iray preview (other versions of Daz Studio have always loaded those automatically as soon as I switch to Iray Preview. Is anyone else experiencing this issue?

EDIT: I found the issue. I had the Strand-Based Hair Editor Tool selected /doh! Apparently, if you have that selected, then Iray Preview is disabled. Once I switched back to the Universal Tool Iray Preview works again.