Quote - why so? as a seperate process it gets its own 2GB allocation from the Windows kernel as per a seperate  program. this is seperate from the allocation Poser has itself or the allocation to the Windows Kernel. so infact, things are improved on the memory front. now, if your refering to how it's passed to this process, thats a different matter ;)

 

It's noted in the readme for Poser 7.  The various memory management improvements that were added to P7 - the program bits that help reduce memory consumption on the fly - are not implented in the external Firefly renderer that gets invoked when you "render in a separate process".  This means that when rendering the same image at the same settings, it can happen that "render in a separate process" will fail due to Out of Memory problems, while the internal Firefly render can still complete successfully.  Note that the internal renderer can still run out of memory, which is sad, but it's much better than it used to be (and much better than the external renderer).

Angel I just picked 2mb out of a bag from the Render Settings screen, I'm aware there are different settings in Preferences but I haven't looked at them since I installed P7 (I think I only changed thread count and nothing else).  There is likely some efficient breakpoint in terms of bucket size, e.g. if it is set to 1 byte that is probably VERY inefficient and may not even work at all, but 2mb works fairly reliably for the type of stuff I do.  I can safely render at much higher resolution and quality than I ever could under P6.

My Freebies