Hi all, I have posted some information recently regarding what some of you call 'the memory bug': http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2275282&Reply=2276129#35 http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2275282&Reply=2277618#66 Why can you spot high resolution renders in many locations? It might be that the artist was considerate regarding the scene setup (hires textures only when needed, lores figures in the background, etc.) or that the artist adjusted render settings according to the complexity of the scene. You don't have to use the most extreme settings to get good quality renders. Often enough you can't tell the difference between a render with middle-of-the-road settings and one with killer settings. Naladae, what you describe sounds like trouble with virtual memory. Especially the fact that Windows is swapping even after closing Poser hints that Poser was using a lot of virtual memory and/or many other applications have been swapped out (i.e. the data has been written to a swap file on disk) during its session. I can pretty much guarantee that with SR1 applied, Poser 6 frees every possible chunk of memory after a render and also tries to reduce memory fragmentation before and after every render. However, once virtual memory is used extensively, the Windows memory manager decides whether it holds on to data it stored previously or frees it and grants more memory to an application requesting it. That unfortunately yields less predictable results than you'd desire. Uli