Quote - Had this happen to me and have seen some others mentioned elsewhere.   So I will add it to the list.

Saving a pz3 (or pzz) with Exteternal Binary Morph Targets turned on can lead to the pbm file becoming corrupted which will cause Poser 7 to crash and close when you attempt to (re)open the pz3.  If you delete (or move) the associated pbm file, Poser 7 will prompt it can not locate the pbm and ask to locate it.   Telling it no will allow the pz3 file to open (allowing you to salvage something of your work) but without any of the morphs (as these are stored in the corrupted pbm file).  

The Save File option (found in General Preference Tab>MiSC) External Binary Morph Targets is set on by default.   You may want to consider unchecking this box (turning it off) until this issue is addressed. 

I am not aware if also occurs with items saved to the library using pbm.  I have only experienced it (and read about it) in regard to pz3 (pzz) files. 

Small nit: it's PMD file (not pbm)

From my explorations of this fun new idiocy, it appears that the PMD format is a work in progress.  There seems to be incomplete thought on how the format should properly handle multiple props and/or figures stored in the PMD so as to avoid problems.  And my justification is obvious - the numerous problems people are having with them!

The fact that they recently added PMD references to scene files (which weren't there previously - possibly before SR2 for P6), shows that the efficacy of the format is unstable enough that they decided it best to have a backup plan - if the Poser PZ3 PMD fails or doesn't exist, at least they might get to an original PMD for each figure/prop that uses them.

Personally, I haven't experienced any problems with PMDs enabled, but the situation seems to be that the format isn't as bullet proof as they pretend it to be.

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone