XENOPHONZ opened this issue on Apr 05, 2005 ยท 12 posts
XENOPHONZ posted Tue, 05 April 2005 at 11:52 AM
It's simply good computer practice anyway -- but until such time as CL gets the P6 memory bug fixed with a service release -- you'd do well to be sure to save your .pz3's prior to attempting a render.
Fortunately, I saved my .pz3 scene last night before clicking on the "Render" button. As it turned out, this kept me from having to redo the entire scene.
The memory bug kicked in, and the open verson of the .pz3 file got corrupted.
So I simply closed Poser, and cleared out the system memory by doing so. I was then able to re-open the saved .pz3 and successfully rendered the scene.
The memory problem is especially active with complex scenes. The more complicated the scene, the worse the memory issue becomes.
I am hoping that Curious Labs gets out a fix for this difficulty very soon.
This is the only problem of any real moment that I've noticed in P6 so far.
And this problem should go away with the first service release.
Other than that, P6 is a program that I can't give too many A+++++++++++'s to. If you're stuck with P4, then you have my sympathy. You're really missing the boat with this one.