Adding to Cart…

Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I noticed this was an issue ever since Iray was added to the render engines. Under your advanced render settings, have you enabled optix prime? If you have, you need to disable it, reboot DAZ, and the issue will fix itself. Just using task manager in windows, i have seen that anything rendered with optix prime enabled will leave a large portion of your VRAM occupied. When you go to render the scene again, you will now need twice as much memory available. To me, it seems like the memory isnt flushed after closing a render, or it stores a copy of the previous render data to use as a baseline for the next. Either way, I can reliably and readily duplicate this issue using my gtx 1060 and any scene requiring 3GB or more in VRAM. Monitor your VRAM use however you wish, turn on optix prime in DAZ, render for a few iterations (or let it finish), close it out and/or save it. Now, check your VRAM. Without closing DAZ, render the same scene again. You'll notice that you now need far more memory, and you may even crash out, or swap over to CPU for rendering. This requires a reboot of DAZ to rectify, too. You can use another camera, load a new scene, or just render the same view again, but it doesnt appear to clear out the memory. However, if you disable the optix prime, the VRAM cleans out nicely after every render. It is something to consider, but hopefully, this will help you.
Just to update, disabling the Architectural Sampler is now weirdly allowing the card to render. I'm on the newest GPU drivers (419.35), which may have fixed it.
Hi guys!
I´m relatively new to Daz Studio and it seems i encountered the same or a similar problem.
I´m on a RTX 2080 with the 419.35 drivers using the latest beta version of DS and i have this scene that i rendered completely fine on my GPU a few days ago. Now i wanted to change something in this scene and after loading it in DS without changing anything it falls back to the CPU showing this "de-allocating memory" error in the log files as soon as i switch the viewport over to iray.
The Architectural Sampler is not and has never been activated for this scene. I´m also not using Optix prime acceleration and i even tried deleting everything that is shown in the scene. Even with nothing left (no HDRI as well) i can´t switch to iray preview without getting this error.
I allready tried falling back to driver versions 417.01 and 417.71 since they have been reported as working flawlessly in a few threads about this issue.
Nothing seems to solve the problem and i´m running out of ideas. It´s probably just an issue with the relatively new generation of 20xx cards and their drivers but i´d appreciate any more ideas to find a solution.
Thanks in advance!
edit: After some more trial and error it seems that it´s the denoiser option that´s crashing my GPU. Everything works perfectly fine without it activated. Still no solution for the problem yet.
I'll check to see if I have smiliar issues with the denoiser when I get home tonight. I will say, though, that I have never had an issue with the IRAY preview mode, only rendering.
4.11 beta is a must for the RTX 2080 cards.
i thought that was obvious by now :)
4.11 beta uses a new Iray renderer aswell.
btw does anyone know if the new Nividia drivers 4.19 works with Daz beta and 2080 cards?
i may try them either way.
I updated to the 419.67 drivers yesterday and everything seems to work fine with 4.11 beta except for my problem with the denoiser. That´s still not solved with the new drivers.
Only obvious to the people who have already researched the issue when the RTX cards didn't work on 4.10 :)
a tip boy
before buying a new gpu check if it works BEFORE you buy it and what it works with ;)
then its easy peasy when you have it up and running