LostinSpaceman opened this issue on Sep 04, 2009 · 101 posts
SatiraCapriccio posted Sat, 05 September 2009 at 10:59 AM
Unfortunately, I continue to get the out of memory errors and crashes after rendering, even though I am rendering to a separate process.
I'm using a less than year old Dell XPS which should be able to handle Poser 8 with no problems. I reported the crashing to Smith Micro, they collected some info from me, essentially told me my specs/drivers were fine, and that they had added my report to the outstanding ticket for similar crashes. Hopefully, SR1 will resolve this memory problem/crashing. In the meantime, I am enjoying Poser 8; I just make sure to save any changes before test rendering. If it's a change I'm not sure I will keep, I save to a new version.
One problem I'm encountered that I've yet to see anyone else mention is that certain textures using the Alternate_Diffuse node display as a glaring white, yet render perfectly.
Quote - If you're hitting this situation, it may help to render in a separate process. That way, the renderer gets its own memory, and when the render is finished, all of it is released as one big chunk. Rendering in a separate process is the way to avoid memory fragmentation. That's why rendering in a separate process was introduced.
Burning within each of us are Fires of Creativity