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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
No I haven't. Is there reason to believe that older drivers do not gobble up as much GPU memory when using DS 4.12?
And how do I uninstall the current set, please? Is is not good enough to use GeForce Experience to install 430.86?
I download the driver and use the installer. Select custom install and check the clean installation option.
OK, thanks. I have done that now.
First test: Render a scene that fell back to CPU at denoise time and crashed Daz Studio 4.12.1.40.
Result. It still fell back to CPU at denoise time with the log full of rend error:out of memory, rend error:invalid argument, illegal memory access, device failed while rendering, A CUDA error occurred: out of memory, rend error: All workers failed: aborting render, etc. DS did not crash this time, but it just stopped rendering. At least I was able to save my scene up to the point where denoise should have started. At that point I have to stop DS 4.12.1.40 and restart it, or it won't use the GPU any more.
Note: The same scene renders in DS 4.11 in GPU with over 1GB GPU RAM to spare, optix pro off, denoising successful, no errors in the log
It won't, as far as I know, significantly affect the memory used - but it may well help with the other stability issues.
While not everyone is experiencing the same issue; the following four issues are being experienced across the spectrum of people who use it.
Any one of those issues breaks the usage of Daz Studio. If the user can't render, the software becomes pointless. Going back to 4.11 is not a workaround, it's a solution because 4.12 is not ready for prime time use. The other solution is to get the main issues worked out- not crashing, not falling back to the CPU when ample resources are available- I don't see that happening any time soon because it seems like the people in charge would rather have users suffer than give them an immediate, viable solution.
To sit there and tell people; "you need to initiate workaround A, B & C to get 4.12 to work adequently" isn't acceptable. If such major changes are being done to the driver of which 4.12 feeds off, then a proper response would be "due to the frequent iRay and raytracing changes being conducted by Nvidia, 4.12 will continue to be a Beta release until such time that frequent major changes are done (as such crashing and GPU to CPU fall back doesn't happen,) where we feel comfortable that Daz 4.12 can now be used with little interruption. Until such time, 4.11 will be readily available for those who need stability. Please note, you can install 4.12 alongside 4.11 if you require the next generation of features."
By not making 4.11 available, you're frustrating the user base. Right now, the user base is requesting stability.
If these issues are going to take some time to resolve, my preference would be for Daz 3D to add the option to render using an older (pre RTX) version of IRay to DS 4.12.
To be fair, only two of these points actually count as bugs (#2 and #3 respectively.) If minimum memory requirements changing between software versions was a bug, then pretty much ALL modern computer software is bug ridden (which isn't necessarily a statement I disagree with) - not specifically Daz Studio. And point #3 seems much more likely to be an Nvidia Iray error - ie. not something Daz's programmers have code access/knowledge to fix if they even knew how.
Not sure I agree with this but I'm not going to repeat all the testing I did (and posted) earlier. I was under the distinct impression that CPU fallback happened well short of the 8GB limit of my card. Now that could be a problem with GPU-Z reporting but Task Manager and GPU-Z seemed to agree. I really had to significantly optimize relatively small scenes just to get them to render in 4.12 (and am still doing so). As you say, points #2 and #3 are solid. I don't use the IRay denoiser at all - I dislike the waxwork like results.
I appreciate that you share your expertise and insights into these topics here. You seem to have inside knowledge or at least well researched and documented data.
I specifically avoided the term "bug", because I am not in a position to know whether they are bugs or deliberate design decisions. So, I referred to them as "issues". My intent was to support @marble in his assertion that 4.12 versions and their associated Iray versions are not smooth sailing, even for non-RTX users. It is too easy to let other people carry the burden of reporting their issues, so I wanted to say that marble is not alone in experiencing these difficulties.
Thank you @barbult. At one point I started to think I was the only one experiencing the problems but then others started posting and all experiencing similar issues to mine. And that is without the additional RTX problems which don't apply to me.
retracted comment...
The fallback due to the optix prime extra vram is not a bug, it is simply a change in the iray architecture. Then I understand it may cause issues for scenes close to the vram limit that were rendering fine in 4.11. But again in this case it's a iray "feature", there's nothing daz can do. If you don't want it the only option is to go back to 4.11, or wait for nvidia to optimize iray.
I have done a clean install of Nvidia Driver 430.86 multiple times now. Every time, Windows Update insists updating it to 432.00. I'm really getting disgusted with this. Is there an easy way to make Windows Update STOP doing that?
I don't get driver updates unless I do them myself, but I'm nto sur how I accomplished that - none of the visible settings look relevant.
Edit: it appears there used to be an option but it was removed - however, these two claim to show a way to set it through more advanced tools:
https://www.windowscentral.com/how-disable-automatic-driver-updates-windows-10
https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html
Thank you for researching all that, Richard. I had found and tried a method using the control panel, but as you said, it no longer works as described all over the internet. These other methods look a little bit scary. I'll have to read over the details and see if I am brave enough to mess with it.
Edit: I only have Windows 10 Home, so group policy edit is not a option for me. That leaves the registry tweak. Or, I saw a link to the show/hide updates troubleshooter. Maybe I can just hide the current graphic driver update that keeps getting reinstalled.
the joy of Windows 10, not having control over your own computer. The only option you've got for total control over updates is to go back to Windows 7. In my case, I have Windows 7 ultimate x64.
Have NEVER had issues with Windows 10 overwriting display drivers with older versions after doing a manual install (not even on a Surface Book.) However, all my machines run Pro - not Home. So maybe that's what makes the difference (would actually make sense for that to be different between the two.)
I have Windows 10 Home on this new laptop and have changed the driver for the nVidia card three times and windows was updated once in the same time and it didn't touch the driver.
In my case, Windows 10 Home overwrote my manually installed older driver (which I regressed to) with a slightly newer driver. I have never had it install an older driver, either.
I have Windows 10, the latest release, and they've added back in control of updates. I've left mine the same because I don't like machines with exposed security flaws, but you can change it now.
Dance of the sugar plum fairy . Animation short film - render in Iray
click to play
I upgraded the driver which didn't work and then downgraded it back to the original and then went up to the latest one without mishaps. I'm just thinking though that I may have done all that before windows updated, I can't remember.
Happened to me too ... I thought I had installed a driver I just downloaded from NVidia and instead of the new version I found that I had an older version and I had no idea where it came from (not one I downloaded). Somehow, I repeated the NVidia install with the new driver and it worked the second time but I am now wary about my Windows 10 Home deciding what's best for me.
@Richard,.
I finally got a chance to try 4.12 on a PC with a fresh windows install, and can confirm that scripts that worked in 4.10, and failed in 4.11, are still broken in 4.12
Looks like what ever was changed inside Studio is a fail for those of us who want to use older scripts for softbody animation.
Which scripts were these, and were they giving errors or just dumb insolence?
I imagine it might have been the freebie breast/glute movement script. It worked fine in 4.10 but not since. Unfortunately, the author of the script kind of abandoned it and has not been back to the forum since, as far as I'm aware. Pity because it was the only reliably working script when when it was released for 4.10 and I have not found a better once since despite paying some money for alternatives.
Good day, I do not have animate lite in my daz3d studio 4.12. How could I fix this bug? Please advise accordingly
Marble is correct, as mentioned many many pages of discussion back ;) .. these are the scripts that were based on seismic math, that provide the best soft-body animation available for Studio.
Here's the most recent page of that discussion.
https://www.daz3d.com/forums/discussion/20208/breast-bounce-script-for-daz-studio-4-5/p9
If anyone knows what, or even why, these scripts don't run now, perhaps Studio can be repaired, as I figure it won't just be these that fail, and we'll slowly see many more questions about why older scripts that run reliably, suddenly began to fail with v4.11 and v4.12.
Richard - I'll copy the error down and post it here or the other thread when I get a chance.
It's not in Window>Panes(Tabs)>Animate (Lite or 2, depending on how long you have had a version of DS 4.x installed on that system)?