Daz Studio 6 Beta - version 6.25.2026.14722! (Updated May 28, 2026)

RustyBln · May 31

I'm using the NVIDIA GameReady-Drivers. First system is a Ryzen 7800X3D, 64 GB DDR5 and a 4090. Second system is a 13600K, 64 GB DDR5 and a 5090. I have the same viewport problems on both machines, so that problem isn't only on Blackwell cards.

Padone · May 31

In general game drivers are not good for 3D applications, as they're not stable enough for the viewport and rendering. A game is much more simple and optimized. For 3D applications to work fine you need the studio drivers, that's what they are for, otherwise there would be no point for them. You can't complain about DS performances if you use game drivers.

Other than that, it is also better to stay close to the drivers used by the developers, so not to update studio drivers if it is not needed, as new versions may affect previous features, or introduce new bugs drivers are not always perfect, even studio ones. To get stable drivers is critical for 3D apps to work fine.

For DS6 the reference studio driver is 576.80, see if the viewport works fine with this driver.

https://www.nvidia.com/en-us/drivers/details/247854/

bluejaunte · May 31

Padone said:

In general game drivers are not good for 3D applications, as they're not stable enough for the viewport and rendering. A game is much more simple and optimized. For 3D applications to work fine you need the studio drivers, that's what they are for, otherwise there would be no point for them. You can't complain about DS performances if you use game drivers.

Other than that, it is also better to stay close to the drivers used by the developers, so not to update studio drivers if it is not needed, as new versions may affect previous features, or introduce new bugs drivers are not always perfect, even studio ones. To get stable drivers is critical for 3D apps to work fine.

For DS6 the reference studio driver is 576.80, see if the viewport works fine with this driver.

https://www.nvidia.com/en-us/drivers/details/247854/

They're the same drivers, just slightly different testing methodology. It's quite unlikely that you will have unusable performance in one but not the other. I'd say in this day and age you're better off researching which drivers are considered good in general because NVidia has lost the plot in recent memory with tons of issues cropping up. Probably too busy with AI...

Richard Haseltine · May 31

Padone said:

@Richard, do you have a dedicated card for the viewport ? Because this may make the difference over people using the same card for the viewport and rendering. Eventually, if this is the case, it may also help the developers.

p.s. Also, for everyone, stating your hardware specifications may help to understand what's the difference among systems which work and don't. Otherwise it's just complaining going blind that doesn't help the developers.

No, I do have a basic AMD Radeon on the CPU but the monitor is connected to the GPU and that is what is used for renders and for the Iray Drawstyle.

Richard Haseltine · May 31

ArtRoulade said:

Richard Haseltine said:

RustyBln said:

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those. $3000 paperweight sitting on my desk until things hopefully improve .

It is seriously embarassing how long this has been a problem that hasn't been fixed yet.

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult.

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA.

Certainly it seems pretty mucxh the same, and perfectly adequate. I didn't time it in FPS, the non-Iray modes (including Universal) are responsive in realtime, as far as I can tell.

Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work.

Please load two storefronts into a scene for further testing and move the camera while in universal or texture-shaded mode. I’m not writing this out of boredom. The same problem also occurs on a third system with an AMD 7940HS and a 4090 Mobile.

I did have two copies of the scene loaded, well the two different files under Environment which is what I thought was meant.

There are scenes where the camera movements works fluently but in other scenes I have the same problem as mentioned.

New York Stores | Daz 3D

Sensu · May 31

Richard Haseltine said:

Unfortunately not every process can be multi-threaded - that requires that the process can be slit down into separate bits that can each be worked on without needing information from any other bit. In the case of adjusting a pose or shape then there are a lot of linked ramifications (one property that may be linked to another) and they al need to be traced through to get a final value, from which the shape can be calculated.

Thank you for your reply and for taking the time.

I understand the situation, though unfortunately, it’s not much of a consolation. Purely out of professional curiosity, I am wondering: what kind of single-core clock-speed performance would actually be required to get characters to move smoothly in real-time within the viewport, without this choppy, delayed response? To be honest, composing scenes this way is highly tedious and frustrating. While turning off visibility for hair and clothing is a standard workaround, honestly, it doesn't yield any significant improvement in performance.

Sensu · May 31

bluejaunte said:

Two hands could let you pour water and stir at the same time. You're not gonna handwrite twice as fast with two hands though. Single vs multithreading.

Thank you for your reply as well, I understand the method.

Sensu · May 31

DoctorJellybean said:

Sensu said:

Why is the Viewport Texture Shaded still single and lonely? A 3D artist girl's case with "lazy" processor threads...

Hi everyone!

I’d love to get some clarity on Viewport performance, because working in Texture Shaded mode lately feels like a bit of an unpredictable adventure. I’m honestly pulling my hair out due to the constant slideshow effect, and I’d really love to understand the whys before I go completely bald and have to wear a wig in front of the monitor.

As I’ve been digging through the technical spheres, I’ve started to get the picture: Daz—my dear, stubborn little favorite—insists on assigning just a single thread to calculate character movement and outfit adjustments, while leaving the others to rest. It’s almost as if it were saying: "We deal with one thing at a time, if you please!"

My Beast (my PC) is certainly not the latest luxury model, but it’s far from a potato: it’s a Dual Xeon system (20 cores, 40 threads) running the studio, loaded with 128 GB of RAM. In theory, it should be purring like a satisfied kitten, but instead, it acts more like a moody little tiger that only moves when it really has to.

But the thing that actually makes me smile... OH WAIT, NO! :) I’m looking at the stats, and I see a single poor thread sweating, but curiously, not even at 100%, while the other 39 threads are cheering on that one poor soul from their comfy armchairs with a beer in hand, as it tries to move that pesky character outfit. Real teamwork, right!

Is there anyone here who could be my hero and explain to a mortal artist: what is the technical reason why Daz is so loyal to this single-threaded technique in the Viewport? Is there any beautiful hope that in the future, the other threads might join in on this little game? Or, if anyone has heard any juicy gossip from the developers regarding modernization, don’t keep it to yourself—bring it on!

If anyone knows a secret spell (or just has a well-proven tip) on how I could convince my "crew" to work together, please share! I’d be very grateful!

Thanks a lot to any clever gentleman or experienced colleague who can gift me some knowledge—or at least a little bit of hope!

It may not be what you want to hear, but here goes.

Studio multithreads the update of individual figures and props in a scene when the geometry on a node is large enough to justify it. However, Studio does not currently multithread the processing of the entire scene node list due to potential inter-dependencies between nodes. They may reexamine this methodology in the future.

Yes, I have already heard about that, thank you very much for your reply.

kyoto kid · June 1

DoctorJellybean said:

kyoto kid said:

...so according to the "Evergreen" release thread (now closed) I take it older versions of Windows (eg. 7 and 8) are no longer being supported..

Supported Operating Systems / Architectures

Windows: 10 (1809 or newer), 11

64-bit Intel/AMD (x86_64)

Microsoft support for Windows 7 ended on January 14, 2020 and Windows 8.1 ended on January 10, 2023. So yes, they are no longer supported.

...thanks for clarifying

So it looks like I'll be stuck on 4.21.0.5 until memory and storage prices come back down to earth as I pretty much need to rebuild a good portion of my system just to comply with the Win 11 TPM requirement (current cost estimate [PC PartPicker] is over 2.300 USD and that's sans GPU [l already have a 12 GB 3060])

I also have the 4.24 general release installer on backup media but it is useless until I can perform the system upgrade as the Nvidia driver ir has doesn't support older versions of Windows.

Enve · June 1

Hi. I'm experiencing severe lag in the latest version (daz 6) when using the "Orbit ZXY" camera tool while NVIDIA Iray is active in the viewport. In version 4.24, camera moves smooth while render iray active

RustyBln · June 1

Padone said:

In general game drivers are not good for 3D applications, as they're not stable enough for the viewport and rendering. A game is much more simple and optimized. For 3D applications to work fine you need the studio drivers, that's what they are for, otherwise there would be no point for them. You can't complain about DS performances if you use game drivers.

Other than that, it is also better to stay close to the drivers used by the developers, so not to update studio drivers if it is not needed, as new versions may affect previous features, or introduce new bugs drivers are not always perfect, even studio ones. To get stable drivers is critical for 3D apps to work fine.

For DS6 the reference studio driver is 576.80, see if the viewport works fine with this driver.

https://www.nvidia.com/en-us/drivers/details/247854/

I made a fresh install (I removed my previous driver with DDU) of the studio drivers you suggested and nothing changed. Still the same laggy viewport as with the other driver.

Padone · June 1

@RustyBln @Richard Another difference I can think of, is 4K vs full HD monitors. The viewport may work fine with full HD and stutter with a scaled 4K. This would probably be a Qt limitation though, rather than a driver issue. One possible workaround may be to set the 4K monitor at full resolution, to avoid the scaling, even if the text will be small. Then of course a 4K viewport is more heavy to process than full HD, but his is unavoidable.

Other than that I have no other ideas what it could be. It's always good to keep the dev drivers though.

p.s. Or one can set the 4K monitor at full HD and see if the viewport works fine. Of course this way the 4K monitor is underused.

ArtRoulade · June 1

Richard Haseltine said:

ArtRoulade said:

Richard Haseltine said:

RustyBln said:

Richard Haseltine said:

ArtRoulade said:

RustyBln said:

Richard Haseltine said:

yonashald said:

Richard Haseltine said:

yonashald said:

Falco said:

I ended up downgrading from the 5090 back to my 3090 so i could use 4.24 again, being able to work more quickly/smoothly in the viewport for production outweighed the 3x faster render times since I can queue those. $3000 paperweight sitting on my desk until things hopefully improve .

It is seriously embarassing how long this has been a problem that hasn't been fixed yet.

Whata re you meaning? DS 4 will never be able to use 50x0 cards, nVidia changed the way they compile the render engne and that cannot be used with DS 4. The only way to itengrate the iray versions required for 50x0 card support is to make changes that break compatibility with DS 4, in other words a full new version. Fortunately DS 6 was already in development and can use the versions of Iray required for 50x0 support.

What I'm refeering to is how insanely bad the viewport on the BETA is compared to DS 4, you can act like it isn't but it is, it laggs/stutters way more than DS4, and considering that is the only real option for people with newer graphic cards, and yeah its a "beta" but I would expect that they would be able to do something about it within a year, but I guess I was wrong.

No one is acting like it isn't so, but it does eem to vary from user to user - which makes it much harder to figure out what is happening and how to address it.

As far as I can see it almost every user here with a 5090 card reported that issue with the BETA. I'm one of them. Just test your own software with a 5090 card and a bigger scene and you should immediately notice the bad viewport performance compared to 4.24. Can't be that difficult.

For example using a scene in Daz Studio 6.25 with New York Stores | Daz 3D on a 5090 the camera movement becomes sluggish even without characters.

In DZ 4.24 with a 4090 everything runs smooth using the same scene. 1st pc - AMD 9800X3D + NVidia 5090; 2nd pc - AMD 5900X + NVidia 4090.

In which mode? I have a 5090 here, Texture Shaded seemed fine, Iray of coursedrops duriing movement but settled down as soon as I stopped, Filament also seems fine.

Basically every mode is barely usable. So you're saying the viewport performance with the BETA is the same as with 4.24 on your PC? I'm sorry to say that, but that's really hard to believe. I tried the DAZ BETA on different PCs, with a fresh installed Win11 and a clean driver installation. It was always the same. Viewport performance on 4.24 was perfectly fine while it's unusable with the BETA.

Certainly it seems pretty mucxh the same, and perfectly adequate. I didn't time it in FPS, the non-Iray modes (including Universal) are responsive in realtime, as far as I can tell.

Don't get me wrong, but you've got a HUGE problem here, and if it isn't fixed, I can easily imagine that, over time, MANY users will switch to other software like Blender, because as it stands now, DAZ 26 is simply unusable for everyday work.

Please load two storefronts into a scene for further testing and move the camera while in universal or texture-shaded mode. I’m not writing this out of boredom. The same problem also occurs on a third system with an AMD 7940HS and a 4090 Mobile.

I did have two copies of the scene loaded, well the two different files under Environment which is what I thought was meant.

There are scenes where the camera movements works fluently but in other scenes I have the same problem as mentioned.

New York Stores | Daz 3D

Exactly those two different storefronts.

I just installed the new preview windows update KB5089573 and my problem seems fixed. I'll have to test it on my other systems.

DoctorJellybean · June 1

ArtRoulade said:

There are scenes where the camera movements works fluently but in other scenes I have the same problem as mentioned.

New York Stores | Daz 3D

Exactly those two different storefronts.

I just installed the new preview windows update KB5089573 and my problem seems fixed. I'll have to test it on my other systems.

Could you please let us know as soon as you have tested it on your other systems.

ramasancar · June 1

I've been considering to switch to Blender, maybe this viewport problem thingy is a perfect opportunity to do that?

I'd just create scenes using 4.24 and do the renders and rest at the blender side?

Please let me know any blender users if they are happy with their workflow.

I read that diffeomorphic does wonders and Chatgpt keep telling me to switch to blender after many years of experiencing daz, it is time to level up my game.

Richard Haseltine · June 1

Padone said:

@RustyBln @Richard Another difference I can think of, is 4K vs full HD monitors. The viewport may work fine with full HD and stutter with a scaled 4K. This would probably be a Qt limitation though, rather than a driver issue. One possible workaround may be to set the 4K monitor at full resolution, to avoid the scaling, even if the text will be small. Then of course a 4K viewport is more heavy to process than full HD, but his is unavoidable.

Other than that I have no other ideas what it could be. It's always good to keep the dev drivers though.

p.s. Or one can set the 4K monitor at full HD and see if the viewport works fine. Of course this way the 4K monitor is underused.

My monitor resolution is 1,920 * 1,200, so that might certainly be a fctoir if others have much higher resolutions.

jjb24 · June 1

I just updated my PC with 3 things this morning and I see a strong improvement in the viewport performance when comparing 4.24 and 6 (2026). My personal opinion is that the main viewport is now useable and before anyone jumps on me for saying this please remember this is only my subjective opinion. I'd still be happier if the main viewport in 6 (2026) was as smooth as 4.24. (details below)

Unfortunately although some of my script products work in 6 (2026) many do not. Of course none of my plug-in products work in 6 (2026) This means my bottom line is that I will still continue to do the bulk of my work in 4.24 and then render in 6 (2026). At least when I have to make a last minute change to a scene before rendering it's now much easier to do so in 6 (2026) than it used to be.

Details:

PC: MSI manufactured: Intel Core Ultra 9 (285K), Windows 11 Professional 64-bit, 128 GB RAM, MSI NVIDIA GeForce RTX 5090

Updates: (I'm sorry to say I did all 3 updates before testing so I cannot say which one(s) are responsible for the improvement.)

1) DAZ Studio 6, build 6.25.2026.14722 (64-bit) Public Build

2) Nvidia driver: Studio Driver 610.47 - May 27, 2026

3) Windows 11 Professional 64 bit installation: 2026-05 Preview Update (KB5089573) (26200.8524)

I did a direct comparison of 4.24 and 6 (2026) on the same PC with both programs open simultaneously which is my normal work mode now. I paid very close attention to the lag and stutter behavior in the main viewport that has been happening in 6 (2026) throughout the alpha and beta releases. I used 2 copies of the same large large scene file [open in 4.24, 'save as' to make a copy, open the copy in 6 (2026)]. The scene file is just over 16 MB in size and includes 14 visible G8 characters, 3 visible G8.1 characters, and 6 hidden G8 characters. A screen shot of the main viewport is attached (one character has a node instance if you're counting characters). Over 95% of the objects in the scene were purchased from DAZ but a few were purchased from 3rd party vendors. I only use the main viewport, I never even open an Aux Viewport pane.

The lag and stutter in 6 (2026) is improved a great deal after the 3 updates but even so it is still present. It is important to say that 4.24 has absolutely no lag and stutter, none at all. The lag and stutter in 6 (2026) is most noticeable when using the 'View: Orbit/Rotate/Bank' and 'View: Vantage/Orbit' controls. When you initiate an action with either of these controls there is often a brief delay and then a small jump when the first movement occurs, i.e. it is not a smooth and immediate start. There is also an occassional small 'stutter' during movement. The lag and stutter is less when using the 'View; Pan/Dolly' and 'View: Dolly Zoom/Focal Zoom' controls. I do not notice any delay when using the 'View:Frame/Aim' and 'View: Reset' controls.

One thing that I believe is important to mention. The lag/stutter behavior is not perfectly consistent and predictable. For example, if you use the same control repeatedly the initial lag may not happen every time but it does happen over half the time. Again, this behavior simply does not exist in 4.24.

Padone · 6:50AM

ramasancar said:

I've been considering to switch to Blender, maybe this viewport problem thingy is a perfect opportunity to do that?

In general there are viewport issues in blender as well, for heavy scenes we have to hide unneeded objects via collections and use the solid mode to animate to avoid delays. So the viewport performance is a common ground here. You don't switch to blender for the viewport, you switch to blender because once the figure is there you can do everything you want with her, far beyond what you can do in daz studio.

Notifications

Daz Studio 6 Beta - version 6.25.2026.14722! (Updated May 28, 2026)

Comments

Why is the Viewport Texture Shaded still single and lonely? A 3D artist girl's case with "lazy" processor threads...

Supported Operating Systems / Architectures

Adding to Cart…