Corrupted/bloated Scenes?

mmoch25

My scene appears to be corrupted or bloated, and if so is it possible to fix and/or prevent?

I have a composite scene made up of a house/yard scene with a ton of plant instances, and one human G8F character, which will now not render the full scene if I try to render it straight away, it won't even calculate geometry and texture totals, (I'm using Daz 4.16). I can render elements of it provided I don't try to render the whole scene first. Once it fails to render as a complete scene, nothing renders, not even a cube primitive by itself. Iray won't even preview the scene.

I thought it was a Vram issue, so I started rendering individual groups with one coconut palm the geometry was 967MB 

Here's the interesting bit.

I started a new instance of Daz and re-constructed the scene, and that same coconut palm geometry is only 90MB, the whole scene is only 835MB W/O the G8F. With the G8F it's 1GB geom and 2.5GB for the textures.

It's very annoying.

There is a 12MB difference in the two scene save files.

I hope that was easy enough to follow.

 

mmoch25

It seems to be an issue with instances. I tested the above scene which might render once or twice, and at one point calculated 11GB for geometry and then failed to render at all, even if everything is hidden.

I deleted all the instances, saved it, reloaded the it, now the geometry is 816MB and Tex 2.5 GB and and it rendered 7 or 8 times consecutively without issue, before I stopped counting.

alan bard newcomer

could be another flavor of the occasional not clearing renders off the video card memory Daz just forgets to compress or wind down from render mode? 
But certainly restarting daz clears it's throat (as it were). 

 

stefan.hums

mmoch25 said:

It seems to be an issue with instances. I tested the above scene which might render once or twice, and at one point calculated 11GB for geometry and then failed to render at all, even if everything is hidden.

I deleted all the instances, saved it, reloaded the it, now the geometry is 816MB and Tex 2.5 GB and and it rendered 7 or 8 times consecutively without issue, before I stopped counting.

If you use instances, make sure that your have set (Render settings) Optimization -> Instancing Optimization -> Memory.
The default setting is 'Auto' and there Iray decides if it uses instances - and this is gambling more or less.
And with 'Speed', geometry instancing is disabled altogether.

mmoch25

stefan.hums said:

mmoch25 said:

It seems to be an issue with instances. I tested the above scene which might render once or twice, and at one point calculated 11GB for geometry and then failed to render at all, even if everything is hidden.

I deleted all the instances, saved it, reloaded the it, now the geometry is 816MB and Tex 2.5 GB and and it rendered 7 or 8 times consecutively without issue, before I stopped counting.

If you use instances, make sure that your have set (Render settings) Optimization -> Instancing Optimization -> Memory.
The default setting is 'Auto' and there Iray decides if it uses instances - and this is gambling more or less.
And with 'Speed', geometry instancing is disabled altogether.

That's it, problem solved, thank you so much.

Memory - 233Mb, 5 renders in a row before I stopped.

Speed - Too big to calculate? Failed to render at all. Why even have a speed option.

I've always used instances, just never enough to bother the renders I guess. I knew that setting was there, I've only ever used it as a quick fix to remove black circles from around eyes, or other issues with geo shells, just swap between Memory and Speed, (I wonder if there's a better fix for that) not realising the effect it had on the renders.

Again thanks.

stefan.hums

mmoch25 said:

That's it, problem solved, thank you so much.

Memory - 233Mb, 5 renders in a row before I stopped.

Speed - Too big to calculate? Failed to render at all. Why even have a speed option.

I've always used instances, just never enough to bother the renders I guess. I knew that setting was there, I've only ever used it as a quick fix to remove black circles from around eyes, or other issues with geo shells, just swap between Memory and Speed, (I wonder if there's a better fix for that) not realising the effect it had on the renders.

Again thanks.

Memory - forces Iray to always use geometry instancing if instances are defined in the scene. Scene preparation for rendering may take a little longer.

Speed - disables instancing, defined geometry instances will be converted back to single geometries. If you have 100 tree instances, practically you get back 100 single trees, what is a big waste of geometry memory. Actually this Speed option is superfluous. The only 'advantage': it may save a few seconds during scene preparation for rendering, but it will not increase render speed like the name could suggest.

alan bard newcomer

and don't use speed with ultra-scenery