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
© 2024 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.