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
I don't have a 5xxx GPU the test with, but with my 12GB 3060 I found that if I fiddle with "Response Threshold(msec)" I can get the viewport to respond a bit better.
The screenshot is the settings I found best for me.
Oddly, higher response time made it smoother.
Can someone else try it out and see if it does anything?
Also, I'm not sure what "Draw Node Avatars" does but turning it off didn't seem to do much of anything that I could see right away in my simple scene.
edit: Ok "Draw Node Avatars" draws nodes like cameras and spotlights. After adding a few to my scene to keep testing I noticed I wasn't seeing them and visability toggled off and on when I toggled it. :)
Sadly, I see on the Daz Blog that both Mimic and Mimic Live! have been officially retired. So no more DS 32-bit Mimic. That pretty much keeps me firmly with DS4 forever.
I'm just getting random crashes after working with it for a while. I'm not doing anything in particular when it happens. Just now I was rotating a prop on the Z-axis.
Windows 11, i9-10850K, RTX-3050, 32 GB RAM
Tried that one myself, a couple of weeks ago, it didn't do {anything}
(Edited by mod)
Same crashes very often for no reason. Just randomly when changing parameters.
Edit: After some more testing it seems like maybe it was the scene that just broke on Daz3d 6 and not the old one. Set up a new and now it works, and after testing the old again, I noticed how much better the new one is, everything is fast, the view port actually has settings that work. A welcome upgrade.
I have installed DAZ Studio 6.25, but I don't see my Poser 11 content directory. How do I tell DAZ Studio 6.25 the path to my Poser content?
You need to add it manually:
F2 - Content tab - Content Directory Manager - select Poser Formats - click the Add button and browse to where it is installed.
Thanks for the advice. I did it by right-clicking in the leftmost column with Poser Formats selected, and selecting "Add a Runtime Directory…" from the contextual menu.
I'm having the same problem, only with dual RTX-5000 Ada cards. Support tells me it's because I'm using third party content. WHAT THE HELL?!
All of it, including the supposedly unsupportable 5xxx series cards, works just fine in 4.24.
In Iray, using the GPU (CPU rendering works in 4.24, of course)?
I lost my whole Daz content and program in a computer reinstall. Installed Daz 6. I now have to redownload everything. But the new C: drive is way too small for my library, so I need to put smart content on my G drive. I watched a ton of tutorials yesterday trying to find out how to do that. I found out how to fix DIM, but not how to chang the path on Smart Content. Can anyone tell me either how to do that or where to find a tutorial? This is so frustrating and I'm on deadline on a project that is due this weekend.
Go to edit > Preferences > Content tab, there's a "content directory manager" button at the bottom of the tab.
Once in the content directory manager you can then edit the current directories to change the path to CMS content cluster, Connect directory, and Poser and DS directories
Thanks!
596.59. As far as I can tell that's the most current Studio driver.
Both. I have a third card that actually drives my display; all these do is render and dForce.
When rendering, simulating, loading unrigged assets, changing viewport angle, posing... once when loading a plane primitive into the scene.
The last log entry is frequently more than 30 seconds old, and is what you'd expect for normal operation doing that task. No warnings, no errors.
This I don't know. How can I tell? The machine was a custom built high-end workstation, so I assume it was done right, but I lack the hardware skills to say myself.
The OP (@almahiedra) has a custom CMS directory (if I read the post correctly). On Windows (10 and 11 IRC) there is a security feature called, "Controlled Folder Access". Those of us who have it turned on have to either disable it for both Studio and DIM or allow both to access all our CMS directories (like the OP and others I have multiple CMS directories on different drives). It's not just CMS, the Postgre database has to be writable too if you moved it.
The settings apply to a single path name; so Windows regards DS4 General, Public and I assume all the others as well as the same group for DS6 as different guys. That's an answer to your question.
For those who experience something like this check out, "Controlled Folder Access". It's in "Windows Security" under "Ransomware Protection"; Microsoft have it well hidden these days but if, like me, you turned it on as soon as it was available it's still on.
Don't change the path to the "CMS content cluster" unless you know exactly what you are doing or you are doing a completely fresh install. The DAZ ecosystem only has one cluster (one Postgre SQL database to be more techy) so changing it in one place changes it everywhere. The cluster can be copied, backed up (by a copy or, perhaps, using Postgre) and moved but I have yet to find a workable way of having more than one. I have certainly tried; I know how to do it but it isn't "workable".
That's not entirely true~~ One can setup multiple cms cluster folders for specific purpose (e.g. content creators can set up unique configuration of Daz Libary / cms cluster purely for the purpose of making products, etc....) and change the cms target by switching Content Sets in CDM as each Content Set can have different cms target folder. The problem is that only one JSON configuration file related to cms connecton / port can be saved / read by DS... However, it can be technically resolved by some ways like using BAT / scripts to update JSON config. file as well as restart postgreSQL service before (or after) loading DS.
If running multiple DS instances even + multiple builds of DS, cms ports have to be also changed as one port cannot be used for multiple cms targets... Setup will be cumbersome but it's still workable.
Studio Driver 610.62 came out in mid-June.