Why would this take 20 minutes?

jmucchiello

I hit cancel after 20 minutes and after seeing Daz was taking nearly 20 GB of ram. I just killed Daz from task manager.

I ran a render with this very same DUF file 30 minutes earlier. So why did this happen? Earlier tonight I had one that sat on retrieving device geometry for over an hour before I killed it.

My system has 128 GB of RAM and I render with a 4090. But sometimes I get this behavior and I can't figure out why.

jmucchiello

After I restarted Daz, it rendered in about 5 minutes. And only use 20 GB of the 4090's VRAM.

Change the HDRI file, and now it's stuck again.

crosswind

That depends on how "simple" your scene is ~~ Some settings in a "simple scene" can also make it "complex" in terms of consumption of RAM / VRAM. For instance, high level Render SubD on figures, high level Line Tessellation Sides on SBHs, no compression for Texture maps, failure in releasing VRAM due to render / Prieview for times ~~~ etc. etc.

WendyLuvsCatz

I often need to restart D|S because it hangs onto memory

scripts like clear undo stack or purge memory work sometimes but more often than not freezes it beyond recovery

also once your VRAM usage exceeds your card it cannot be cleared without restarting

jmucchiello

crosswind said:

That depends on how "simple" your scene is ~~ Some settings in a "simple scene" can also make it "complex" in terms of consumption of RAM / VRAM. For instance, high level Render SubD on figures, high level Line Tessellation Sides on SBHs, no compression for Texture maps, failure in releasing VRAM due to render / Prieview for times ~~~ etc. etc.

Except it renders this scene in 5 minutes after a fresh load into a fresh launch of Daz. That doesn't sound that complex. I generally don't do scene optimization if rendering "works".

Could someone point me at the clear undo script someone mentioned above?

Thank

crosswind

jmucchiello said:

crosswind said:

That depends on how "simple" your scene is ~~ Some settings in a "simple scene" can also make it "complex" in terms of consumption of RAM / VRAM. For instance, high level Render SubD on figures, high level Line Tessellation Sides on SBHs, no compression for Texture maps, failure in releasing VRAM due to render / Prieview for times ~~~ etc. etc.

Except it renders this scene in 5 minutes after a fresh load into a fresh launch of Daz. That doesn't sound that complex. I generally don't do scene optimization if rendering "works".

Could someone point me at the clear undo script someone mentioned above?

Thank

Go to the product: Default Resources for DAZ Studio

There's a script named Purge Memory which "clearS undo stack" in RAM... however, this script has nothing to do with VRAM.

markusmatern

When rendering in IRAY check figures or clothing with high levels of Render SubD Level (Minimum) in Parameters -> General -> Mesh Resolution or high settings of SubD Displacement Level for shader settings with surfaces having Displacement activated. Look under Surfaces -> Geometry -> Displacement -> SubD Displacement Level

jmucchiello

markusmatern said:

When rendering in IRAY check figures or clothing with high levels of Render SubD Level (Minimum) in Parameters -> General -> Mesh Resolution or high settings of SubD Displacement Level for shader settings with surfaces having Displacement activated. Look under Surfaces -> Geometry -> Displacement -> SubD Displacement Level

 Will this solve it hangs during "updating geometry" for a duf file that it rendered in 5 minutes just a few minutes ago?

I am well aware that SubD exists and can add greatly to texture sizes.