I'm getting corrupted pz3s with several different situations. Each problem results in a pz3 that when re-opened comes up with the Doc Display changed to wireframe, some textures and figures missing, no lights, some figures unconformed, etc. Here are 3 situations:

1. Sometimes when I use the "delete lights" script, either the one that comes with P6 or the updated version by Ockham, P6 freezes. When I use Task Manager to shut it down, and reopen the file, I get corruption. This just happened with a file as well as a copy of that file which I saved before I tried the script. Ie, it destroyed not only the original, but its copy. How could this happen? I note that some .shm files were left over that they had in common.

2. Occasionally, the material room will become unresponsive to my mouse. Ie, nothing I click on reacts, and I can't change any nodes or anything. The rest of Poser still seems to work when this happens; I can go back to the Pose room, and back to Materials, but no nodes or anything reacts to the mouse. But when I close, or save and close, and reopen the file, it is corrupted.I don't have any mouse troubles with any other applications.

3. Occasionally, a Firefly render will get hung up before it reaches the "rendering" step. Sometimes "Cancel" works, sometimes it doesn't, in which case I've got to close Poser with Window's Task Manager. Sometimes after this, the file is corrupted. I've tweaked my bucket size, but it can happen with settings from 64 to 512. I don't know what triggers this. I know other folks have had trouble with "Cancel," but does it corrupt your file when you have to force Poser to close?

It doesn't matter if I save the file immediately before performing one of these operations.

I'm using WinXP, 1 gig Ram. P6 with SR1. These are very small scenes, just one figure and some clothes. Thanks for any advice.

Message edited on: 09/24/2005 06:05

Gallery