I've been having trouble with some props and such "freezing" up -- that is, getting stuck in a state where I can't use the morphs.

I wasn't sure what was causing it -- thought maybe it was loading morphs into an attached prop rather than the body of the figure.

But now I believe it happens when I use REVERT.

The really annoying thing, is that this seems to corrupt the file I'm reverting to.

So even if I close the filed own and reopen it, the error persists.

I guess I could just re-load all the props and such, but I'd really like to figure out the root of this problem and fix it.

Any ideas?

I'm running Poser 9 on Windows 7 64bit, just a basic machine.

Thanks.

-- Steve

P9 does have problems with attached props.  It tends to forget that they're attached. 

I tried a quick test with a little attached prop that contains a morph.  Couldn't make it forget the morph after Revert.  Tried it again with Binary Morphs turned on; still didn't forget the morph.

In general the Binary Morph thing is a bad idea, but it doesn't seem to affect this, at least for my simple test.  Do you have some other setting that might possibly get in the way? 

I use Xamvera's perfect morphs on (most of) my characters.

http://www.renderosity.com/mod/bcs/index.php?ViewProduct=94928

Could all the channels that uses contribute?

Not exactly sure what a binary morph is.

The last time this happened, I "lost" the ability to use morphs on an attached (genital) prop, on the character's hair, and it screwed up an adjustment I'd made on a conformed top, too.

The hair seemed to show the (adjustment) morph -- as did the others -- but they didn't actually do what they were supposed to.  When I replaced the hair, I could morph it again.

So, I've assumed that what was happening was that those files in the scene were being corrupted somehow.

But, really, I'm close to being completely out of my depth trying to figure out the inner workings of the program.

I just don't want to accidentally nuke what I'm doing (again), and have to start over (again).  So if I could figure out what the issue is, and if there's some kind of fix, that'd be great.

Right now, I've reverted to saving multiple versions, so I have a "go back" option.

Thanks for your reply and help.

-- Steve

After reading the readme on that product:  Sounds like it creates morphs within Poser on a 'temporary' basis.  I can't tell if those morphs would be automatically saved into the PZ3.

If you've used that product after loading the PZ3, and then you revert before saving the PZ3, I'm pretty sure those morphs will be lost. 

If your general preferences are set to use Binary Morphs, then those changes will DEFINITELY be lost.  The Binary Morph trick saves all the morph information in a separate compressed .PBM file outside the regular CR2, and those PBM files will definitely not be changed by the Xamvera product.

Look at your prefs. Ctrl-K, find the Misc tab, uncheck "use external Binary Morph" and see if that helps any.  As I mentioned before, the Binary Morph is an unnecessary and usually bad option anyway.

I'm away from that computer at the moment, but I had noticed that the program was saving 2 files for some poses -- which, at the moment, I'll refer simply as the:

Red thumbnail file

The gray thumbnail file

The red one is the usual pose file.  I suspect the other -- which isn't always present (or at least hasn't been) -- may be the other type you mention.

I don't remember turning that option on, and if you say it's a problem, I will happily turn it off.

But, being curious, can you tell me why it would be bad?

Thanks.

-- Steve

I think the gray (thumbnail) files have PMD as their extension.

And I did un-check the separate binary file.

And then noticed that my red (thumb) file got substantially larger.

Is the two-files system an atttempt to save space?  (At the expense of accuracy?)

Yes.  The concept is to optimize Poser associated file size (cr2's, pz2's, etc) for quick loading and disk space conservation.  But, unfortunately, under some circumstances the PMD files can become corrupted.  This is prevalent in earlier versions, however SmithMicro did fix the problem with P9, I believe.  Make certain that you have the latest SR installed.

Yeah, I have SR 3.3 installed, I think.

It was the latest, last I checked.

I had to reinstall late last year when the program stopped working entirely, so I cheked for updates then.

And I looked the other day, too, and didn't find anything newer than I had.