Although, I bought P5, loaded it up, and found that I totally "Disliked" it, I bought, Poser6, and I am Happy to say, "I think this is going to work for me!" I have found it more "user" friendly", and more "familiar" to the dials that are within P4-ProPack. I guess, that was the problem for me with P5............For me there was not an "easy" transition.........but I think P6 will do it. (:

Outside of the memory bug (which will hopefully be fixed soon) P6 is the premier edition of Poser so far. Excellent. I recommend it highly.

Same here. I just finished copying my homemade Props, python stuff, and active scenes into the P6 runtime. I never did that with P5; it just felt wrong from the start, and never improved enough to be worth the switchover.

I'm worried about corrupted pz3s. Is that related to the memory bug? In all these years I never suffered a corrupt pz3...not in P4, P4/PP, or even P5. P5 would choke and lock up but my file was still okay. My files are usually pretty big...should I hold off using P6 til they fix it? (I know I can save multiple files but I'd rather not.)

I'm worried about corrupted pz3s. Is that related to the memory bug?

Yes. Directly related.

For some reason, as you work on a scene, P6 gradually chews through your system's RAM until the memory runs out. At that point, you get an "out of memory" warning dialog from P6. This is then followed by a corrupted file.

In my case the file corruption consisted of missing textures. And I've only experienced this type of crash during attempted renders.

As has already been mentioned in other threads, the best work-around is to save incremental backup copies of your .pz3, and exit & restart Poser between each save. Exiting Poser clears out the memory.

It's irritating, but necessary with complicated scenes. Until Curious Labs comes up with a fix.

One problem I'm noticing after more use is an OpenGL oddity with Hither and Yon. The OpenGL has trouble with objects that are thin in the Z direction. Looks like there's always a way to bracket Hither and Yon so that the scene looks right, but the bracketing takes a LOT of trial and error. Would be nice if Poser could set this automatically. Above is the preview using original Hither setting (.0016, I think). Note the eye-pupils and doorframe are messed up. Below is improved P6 preview with Hither set to 2. It has always set the camera's scale automatically when you change focal length; seems like this new adjustment could be done as part of that process.

Thanks Xeno. Looks like I'm still stuck with PP and can only use P6 for play til they fix it. Hmph, same situation I had with 5, only they never fixed it ;)

Hmph, same situation I had with 5, only they never fixed it ;) I get the feeling that this isn't your Dad's Curious Labs......so to speak. I expect that we'll see a service pack in the near future.

They DID fix the memory leak in P5 ... with the last service release (or perhaps even the one before that, but I'm pretty sure it was the last.)

So is this a NEW memory leak issue? From XENO's description is does sound very different. The previous memory leak was associated with RENDERING ONLY. Rendering large sequences of frames (like most renders for anyone who animates) would cause lock-ups and crashes as Poser failed to release memory.

-Tim