Hi all, here's a word regarding the "Out of Memory" message. Let me point out a few things (partially quoted from a statement I made in this forum earlier on): There isn't or wasn't "the" memory bug. There were some problems in Poser 6 before SR1 that made an out of memory message occur even when it shouldn't have. These problems should be fixed now. I'd dare to say that the render engine is fairly solid in SR1. There are also a number of improvements to texture handling and FireFly itself that will enable you to render larger scenes or scenes with more challenging settings. But there certainly is a limit to what is possible. Once you're getting closer to a million polygons or 30 hires textures, you will have to lower the render settings a notch (btw, the FireFly rendering tutorial in the Poser 6 Tutorial manual PDF explains how this often doesn't even affect your final result). The settings labeled as final are very aggressive in terms of resource needs. It is possible that at such render settings, a complex scene consumes more memory than an application can use on a 32 bit Windows system (2 gigabytes). That's why there is a memory check during rendering and that's why there is a message that suggests lowering those settings. This is all normal operation of the application. Please also consult the above mentioned FireFly rendering tutorial for details on this matter. Please render responsibly :-) If you experience that lowering the render settings doesn't help, if your scene is not complex (100,000 polygons or less, no 4k by 4k textures, no texture filtering), then that is not normal and considered a bug. In such a case, please contact e frontier tech support through http://www.e-frontier.com/go/emailtech I if you haven't done so yet. Setting virtual memory to system managed might help in some cases. The more adventurous users can also play with the newly introduced render memory preferences - tweaking the adaption threshold can make FireFly use more or less virtual memory before it reduces the size of a render bucket. Or you can switch off the automatic adaption of the bucket size. If you know the perfect size for your current render, it might render a bit faster because the adaption takes some time when it occurs. Setting the memory limit buffer closer to 0 MB takes FireFly's safety buffer away, squeezing out some extra memory (be careful with the latter two settings, those can affect stability). Hope this helps, Uli