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
Wow. The fact that the new RTX drivers that are fixed (no longer grant kernel access) won't allow for lengthy animation renders is really starting to run my patience out the window.
Wake up the next day - ready to start the new project for work - only to find that only a third of my animation rendered and it's now stuck calculating what happens between each Iray iteration - taking f o r e v e r per iteration, so the per frame is more like (just guessing) twenty or more minutes per frame instead of 39 seconds.
Another peave is that Iray Render Progress window no longer stays glued to the bottom (newest info) - instead holding its position between each frame. I know... who cares, right? Well it's a PITA - especially combined with the above impossible situation. Argh!!!
Right. I did that.
But I was warned that previous drivers have a massive exploit vulnerability granting access to our kernel
That means that an application can attack the PC using the nvidia drivers. Again it is a risk mostly for gamers or people who install everything without knowing what it is. I don't think blender or daz will ever attack the PC via the nvidia drivers so we're safe about that.
Oh... thanks ! It's great to hear we're safe about it. I'm updating to 566.14... hope rendering will work with it...
Edit: NSD ver. 566.14 works well with DS 4.22 / 4.23, so far so good.
Okay, so the "Compatible Software" field on all products now says "DAZ Studio 4.22" and not 4.23 anymore. The new scene dialog shows a software update for "DAZ Studio 4.22 Out Now". Has 4.23 fallen out of favour?
The product library installer is still 4.23.0.1 so I don't think 4.23 is withdrawn.
Anyone else finding that huge amounts of content (especially hair and poses) no longer work since this update came along?
Either I get an error message (usually for the poses) or for the hair I get these large light grey boxes appear instead.
Never happened before the update and it's usually for content I have used without any problem for a long time.
Very unlikely to be the update itself, that sounds like a content path (if you get errors about missing files) or database issue.
Does anyone know if 566.36 works proper? The wife has 560.94 and just updated DS and now running into the issues with rendering and iray. NVIDIA is very unreliable anymore. She was doing thumbnail renders for a new pack, and they were taking 2-3 min and now since the DS update they are taking 15+
I've been noticing longer render times too.
NSD 566.36 works properly on my side. Latest DS + NSD is always slower than older versions in terms of rendering... but I've not experienced that serious, 3 mins to 15 mins +... usually appr. 5% slower than before at average.
Same here
Maybe because her currently installed driver is too old? IDK what version of DS she was on to give me a better picture of what could be going on. She broke the #1 cardinal rule of a PA. Never update while in the middle of making a pack. She is an "if it's not broke don't fix it" so she's bad with updates on everything but for some reason she wanted to update now.
Well, the Geometry Sculptor is Much improved! I do hope that they continue to give it more lovin tho!
Initial Issue (October 18th)
"an illegal memory access was encountered" Iray rendering breaks, gives that message, falls to CPU, and never goes back to GPU. This was first found after updating to the new DAZ Studio while also updating a new GPU Driver. Before that, I could render hundreds of frames on GPU, with some CPU renders sprinkled in, but it never gave that error message. The first CPU render after it fails always had to be re-rendered because it has frame tearing, or something, not sure how to describe it, and that never happened in the past.
Initial Solution (October 21nd)
I rolled back from Nvidia Studio Driver 565.90 to 561.09. This made it possible for me to get more renders done, sometimes I can do hundreds depending on the scene, but it was still visibly slow. I would randomly have the same issue where I fall back to CPU with frame tearing. It can happen 100 to 200 frames in, or even as little as 20, as I just had happen. This is extremely frustrating as I leave it running when not home or sleeping, and hope it gets a lot of frames done, but this issue messes that up. In my last render, it only did 20 GPU frames and then 80 CPU frames in 10 hours. That would be like 300+ frames on GPU...
Update As Of Today (December 17th)
Since I was still having issues with renders even on 561.09, I finally tried the newest Nvidia Studio Driver 566.36, released December 10th. I immediately saw it take forever to start doing a single GPU render, and then after that 1 frame, it went to CPU. That is WAY worse than what I was dealing with.
I am going to try falling back to Driver 560.81 and see if I stop seeing the issue. If it keeps happening, I'm going to assume the issue also has to do with DAZ itself. I don't know what driver I was on when I updated to 565.90 in October, it is possible I was on an older one, so we shall see what happens next. So far, I at least am back to getting GPU renders... I just don't want to see it fall to CPU with that error...
Updated After Sleeping:
I got 340 frames done before it gave the error and went to CPU.
The Shader Mixer doesn't like the Toon or Toon Outline blocks at all any more.
Now that a new public beta is out, does someone have an idea when the general release will be update to 4.23.0.4 ?
It could be useful for MacOS users and would avoid a lots of headaches to people who don't necessarly follow closely the developpement of Daz Studio and may have missed the warning about Daz 4.23.0.1 on MacOS having problems with plugins.
There will be an update to General reelase when Daz is happy with the current build, so it isn't possible to guess. I would imagine not before there is a newer Iray, given that the change log shows one added and then removed, but I don't know if that will conflict with other priorities.
How do I parent in place in this version? If I move an object to say the figures hand and then parent the object to the hand the object flies off somewhere, this didn't happen in previous versions
Should be the usual places - check box in the chnage parent dialogue, or checkable item in the Scene pane option menu. It is present in the option menu and working as expected here - try Window>Workspace>Update and Mrge menus, or try reloading the layout.
It seems like Daz 4.23 has a memory leak. For some reason, denoiser works only after 3 renders. The 4th one is all grainy. In 4.22 i had like 6 to 7 renders before denoiser stops working. I have quite a powerful laptop
Specs:
amd ryzen 7 6800H with Radeon Graphics
Rtx 3050
16gb Ram
I have noticed this too - it's very annoying. The weird thing i've noticed is that the number of frames it seems to manage always seems to be the same number. In the last animation i rendered, it would do 90 frames, and then stop. I would save, close, re-open and try again, and it would render another 90 frames and then stop.
It always used to stop when it ran out of memory before this update, but it seems very odd that it manages the exact same number of frames before the memory runs out each time...?
Hello to all! Recently I updated DS to 4.23.0.1 and encountered a couple of issues with rendering and Genesis 9. The one with IRAY render is the famous pink or purple renders problem, which was reported several times at the forum. When I try to run render in IRAY with my CPU, I get pink textures instead of regular image (I have not any Nvidia GPU, but formerly my CPU was workable for simple Iray renders, when I used DS 4.20 beta). But the solution was to find missing freeimage.dll and put it into DAZ 3D>DAZStudio64>libs>iray. I haven't found any freeimage.dll in the setup package of the general DS 4.23.0.1. How to fix it?
The other unusual problem appeared when I tested Face Transfer 2 with Genesis 9 figures. Formerly in DS 4.20 it worked flawlessly with Genesis 8, but in DS 4.23, when I run this plugin on G9, I get constant crashes with an error message like "DAZStudio.exe caused ILLEGAL_INSTRUCTION in module "C:\Program Files\DAZ 3D\DAZStudio4\avatar_sdk_metaperson_daz3d.dll". I have the latest update of Genesis 9, with all clothes and necessary presets. The crash happens when this plugin reaches the stage of generating shapes and textures. What's the issue? Maybe it requires a larger photo to generate a compatible texture with Genesis 9 base head image? The last one I used was about 1500x2000 px and I got a crash all the same. I can attach the last log, here is it. When I use Genesis 8, I don't see such a problem, and I wonder why old Genesis 8 does not require any clothing for the plugin to work.
My system is Windows 7 x64, with AMD CPU and double AMD GPUs, about 6 GB of RAM, it it's important. Can it be linked to my hardware?
If you go to https://www.daz3d.com/forums/discussion/666011/daz-studio-4-23-0-x-nvidia-iray and search for freeimage you shoild find an explaantion - though I think still being on Windows 7 may limit your options.
Genesis 9 is supported by FaceTransfer 2, on which you get three free goes and then are limnited to previews (with a watermark on the maps) - again, I have a feeling being on Windows 7 still may be part of the issue.
Ok, thanks for the answer. So what are minimal system requrements for this OpenImageIO plugin? Should I have Windows 8 or 10, and what CPU does it need at all? (I mean, can it work with AMD CPU with updated OS, or it works with Nvidia cards only?). As I remember, Freeimage was slow as a turtle and noisy, but less capricious, it worked even with limited RAM.
What for Face Transfer 2, how can it depend on a specific OS? If FT 1 works with Win 7 and Genesis 8, maybe there is some bug in the FT2 plugin itself? I hope the author will update this tool further, maybe I will see any solutions of this problem.
I am not certain of the system requirements for this particular version - OpenImageIO is a widely used standard, but the way in which it is compiled for iray may introduce limitations.
I am not saying there is a compatibility issue with Face Transfer 2, though it cannot be ruled out - as far as I am aware it does use third-party libraries so they may have requirements.
Do bear in mind that Windows 7 is several years past its end of life - and while I am still refusing to update to Windows 11, and so have little room to lecture, holding on to an old version of the OS is inevitably going to become increasingly problematic.
Hello Question not Comment
I have read a lot of the forums. Hoping not to repeat a question. If I missed it I apoligze. Since the update to 4.23 my render times are three times longer. Could be my hardware, I know a lot of things affect render times. I feel this is my primary issue: I get these messages during rendering: =
Iray (Scene Traversal) : Initializing update
Iray (Scene Traversal) : Retrieving journal and checking for changes
:::Everything is locked during render for me how could things change? Thanks for any insight. Will
I don't know if DS will respect the Windows font-scaling in WIndows 7, it will in later versions.
You can adjust the colours, by selecting another style or by customising the style settings (both from Window>Style).