Render Windows holding memory - Close 'em!

3dOutlaw

I was doing a lot of renders, and comparing results, using the open render windows, and I noticed my memory usage for DS was like 6+GB 

I closed it all, restarted DS, opened the scene, and 1gb.  I then rendered. looked at the render, looked good, checked memory, 5+gb!!!  Great googly moogly!  

Then I closed the render window...back to 1gb.  

Moral of the story?  Close 'dem render windows!

RayDAnt

Yeah. This is actually a little known FEATURE of Daz Studio with Iray. Each and every render window represents a wholly independent Context (aka instance) of Iray which can be started, stopped, resumed, extended, or even restarted via parameter tweaks to the hidden pop-out settings pane found along the left-hand edge of the window. In order for this to work, Iray has to retain all loaded assets for that Iray Context in memory up until the point that the render Context is shut down (what happens programmatically when you close the Render window) rather than if/when the Render automatically stops.

onix

This does not seem to be documented anywhere but almost everyone finds it out eventually LOL

although the problem is not with stem ram but with GPU ram which gets consumed by each window. (iRay preview is one of them too so you need to turn it to texture shaded before trying  render your picture) 

I even submitted a ticket to Daz to do something about it, because you occasionally forget to close previous window which makes iRay revert into CPU and you need to restart everything to continue.

Pretty annoying thing especially that if you click render you cannot cancel it anymore for quite some time. and even if you try to close an extra window quickly it is already too late.