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

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2406795

Do you have External Binary morph targets enabled? If no,,Did you save or use any characters in library with .PMDs (binary) enabled prior to disabling it? Have you "cleaned out" any folders where you save your PZ3's? I do NOT want to start bad info but unless you are making mechandise, or are incredibly impatient, you do not need "Binary targets". May I suggest,,,get everything the way you like in matroom, rendersettings and in poseroom. Scroll up to P6 in character library. EDIT> Set Prefs> uncheck "Use Binary Morph Targets" and anything else that suits you. Set Prefs. EXIT P6 Reinstall P6 (as before) and SR1 Reboot Start up P6 and go to EDIT > prefs to be sure it is still the same (this I cannot remember). If you change anything in prefs, close P6 and reopen it to take effect. There will be some residual problems for a while until P6 clears itself of binaries. Open and resave your characters in Figures This is a bandaid. Not a cure

Richardson, many thanks for your tips and the link to the related thread. >Do you have External Binary morph targets enabled? < I don't now, but I did some time ago, when I first started using P6. I unchecked it after getting some corruption. >If no,Did you save or use any characters in library with .PMDs (binary) enabled prior to disabling it?< Undoubtedly I did. I think you have fingered the culprit (the .pmd system). I will do the uninstall/reinstall as you advise. Thanks again!

With any luck, the previous suggestions will have fixed the problem. In the event that they don't, how big is the file that was created by the save (you mention that they are small scenes, but how big are they in system terms)? I have seen the problem you describe in your initial paragraph and something similar to the one in your second item 2) :0. I have only seen the first one in Poser 6 and I have mainly seen the second one in Poser 5, but I never knew it to corrupt a saved Poser file (I thought that was a Vue trick). Something like this was discussed in a thread http://www.renderosity.com/messages.ez?Form.ShowMessage=2410026 and the URLs posted there did seem useful. Both these problems (in my case) do seem to me to have been linked to the actual size of the file on disk. This PC has 2GB of memory, which is as much as Poser knows what to do with, but it still hits the buffers when I try to render a large scene. Dizzi points out in the thread above that, if Poser gives up on a save, it's the lights that are first thing to get chucked overboard. I can't understand how the action of saving or rendering a subsequent save can corrupt a previous save, but I am NOT doubting that your previously saved files are corrupted. I suspect that they are saved intact, but that Poser can't re-load them. I tried deleting all of the unused morphs from figures in my scene. It did help, but I had to go back to an earlier save and re-do one whole figure from scratch. I hope that some of this helps!