- This topic has 10 replies, 7 voices, and was last updated 4 years, 10 months ago by
.
-
Posts
-
I've run into an issue of late, which crops up only when I have a heavy scene. I can render 1-2 scenes with no changes in content or lighting (just poses) just fine in Iray with full GPU, but on the 3rd render or so, it kicks to CPU, and slows waaaay down. Log file says I ran out of RAM, yet with zero changes in the scene content, well, how? Do I have a memory leak? Does the NVIDIA driver or the Iray engine retain artifacts or unreleased RAM after a render run?
Restarting DAZ Studio fixes it, but only for 1-2 renders or so.
Laptop is more than sufficient: GTX 2070 w/ 8GB, 32GB system RAM, 10th-Gen Core i7 gaming rig.
Not sure yet of the cause. I've upgraded the driver, and still no change. The laptop is running Windows 11, but has been on W11 for weeks, no problem (though it did do a small update earlier this week... I may start there.)
I'm just curious if anyone else has seen similar issues under similar circumstances?
DS is not well optimised for memory use.
If you are rendering intensive scenes, it is as well to restart DS every so often to avoid the behaviour you mention.
🙂
Yep, I restart DZ often to avoid this. Sometimes even force DZ to close window if it’s stuck in its ‘I’m clearing a scene , I might be a few hours!’ Just faster to restart. (And this is with a 3090, i9 etc) Plus clear out unused morphs to another folder for faster loading Genesis 8 etc.
It is frustrating though.
To clarify, it's vram, not ram, that is causing fallback to cpu. Iray (not Daz) does not release vram completely after each render - the only option is to restart Daz (and therefore iray) to flush vram. Nvidia aren't particularly interested in optimising for hobbyists; they'd much prefer we all go out and buy 48gb rtx 8000s.
Scene Optimizer is most useful when you can't normally render a scene using the gpu at all. Use selectively eg background objects that don't need full details because they don't occupy enough of the final render and/or will be out of focus. That said, if you're rendering out to 1080p and you're not doing a closeup of a subject then you might get away with 2k textures for your characters. Even 3k will reduce texture overhead by over approx 45%, compared to 4k.
This has been a bug for years and it's the main reason I've switched to Blender to render scenes. I was spending more time saving, quitting and reloading between renders than I was actually rendering.
Iray can look amazing, but the amount of hoops you have to jump through to get to a finished render is just not worth the effort to me anymore. I don't know if Iray's inability to release VRAM is a 'feature' of Daz's implementation or if it's a problem with Iray itself, but it's ridiculous that we still have to quit and relaunch after a couple of renders, especially considering how bad loading times are when having more than a few morph packs installed.
Cycles would be nice... quite nice.
They puttered with Filament for awhile, but that went approximately nowhere. Pity - Filament has some potential IMHO.
@D0gg0d "I find it easier and faster to just restart Daz."
Ditto for me. Sometimes I do a computer restart.....is there any sense in doing that?@Frank21, A complete system restart will make sure that your memory (RAM and VRAM) is as empty as possible, which might be a good idea if you use task manager to kill Daz when it's taking it's sweet-a** time quitting as there is a (small) possibility that memory won't be properly released. Windows 10 at least seems to be pretty good about handling memory clean up though. That said, if you're doing multi-hour renders. it's probably a good idea to start with as clean and stable a system as possible.
If I do a lot of other stuff like web browsing or Ive been messing with other programs Ill reboot.
- You must be logged in to reply to this topic.
