Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
Glass only show's it's reflection. If you want to see it outside of reflection you can set "Max Refraction Weight" in draw settings to a value less than 1 or you can use universal and set it's override to wireframe.
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!
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.
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.
I just upgraded DAZ 6 to the latest version (6.25.2026.14219) and I updated to the NVidia drivers to the very latest version (610.47 - Release: Tue May 26, 2026) and now Daz 6 won't render. See Troubleshootng info below:
2026-05-27 08:57:21.969 [WARNING] :: \src\pluginsource\DzIrayRender\dzneuraymgr.cpp(418): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: Cannot render: found no usable devices. Please update your NVIDIA driver (www.nvidia.com) to at least 576.02, or enable CPU rendering.<br /> 2026-05-27 08:57:21.971 [ERROR] Iray :: Invalid parameters (null pointer).<br /> 2026-05-27 08:57:22.081 [INFO] :: Saved image: C:\Users\jande\AppData\Roaming\DAZ 3D\Studio6 Public Build\temp\render\r.png<br /> 2026-05-27 08:57:22.081 [INFO] :: Finished rendering.<br /> 2026-05-27 08:57:22.095 [INFO] :: Total Rendering Time: 1.55 secondsAs I'm pretty sure I got an NVidia driver version >576.02 I'm at a loss here.
Should I downgrade the Nvidia driver? Or is there another solution available? Thanks for help/guidance!
Is your GPU listed in Render Settings - Hardware tab?
Yes, it is; see screenshot attached. And while looking it up, I also noticed the checkbox "Check GPU driver version". If I uncheck this, Daz 6 renders.
However, I don't think this is the correct behaviour... The new driver is newer than the required driver, so, it should not throw an error if this checkbox is checked...
It could be the actual driver itself. There have been issues in the past with new drivers, which were then fixed with the next driver update.
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.
Techniques like breadth-first parallelization - grouping by hierarchy depth or decoupling morphing from skinning could resolve these bottlenecks without compromising data integrity.
Moving toward a more data-oriented design would allow the software to leverage modern multi-core and GPU performance, which current high-poly characters clearly demand. I hope to see the architecture evolve in this direction.
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.
Frankly IMO this was changed from Alpha to a Beta release way to soon
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.
I agree with everyone complaining about viewport performance in 6.25 with a 5090. It's simply too frustrating to create scenes and pose characters with the jerky viewport. To make lemonade out of the situation I've learned to use 4.24 and 6.25 simultaneously and I kind of like it. I do pretty much everything except rendering in 4.24 and then do the rendering in 6.25. While a scene is rendering I use 4.24 to create the next scene. Of course there is a performance hit but with a high end PC it's not too bad and I suspect most people who can afford a 5090 have a pretty good PC. I know this workflow isn't for everyone because we have different needs but for story telling where characters are re-posed in the same scene a number of times it's not bad. It also has the benefit that all the scripts and plug-ins you own work in 4.24 where you do the detail work. This way you don't have to worry about script and plug-in upgrades for 6.25 and potential upgrade charges.
This next part is a naive guess on my part and if it's crazy I apologize for wasting your time. I don't know how things work 'under the hood' but if supporting the new 'Universal' view option is responsible for the performance issue then maybe it's time to back the feature out? Since 6.25 is now a beta it would be a significant setback to return to alpha but viewpart performance has to be restored. Although the universal view is a nice idea there are other ways to increase contrast between objects when the colors are too similar in texture shaded. For example, switch to cartoon shaded or filament temporarily. I miss cartoon shaded in 6.25 but filament is still available.
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.