Quote - I always try to remember to save before I do something risky, such as render, run a cloth simulation, or turn IK off. :) Sometimes I forget to save, sometimes the supposedly innocuous little thing I was doing turns out to have been more risky than I expected; but on this occasion, as far as I knew I'd saved a perfectly functioning scene without mishap. How wrong I was...

The trouble, I find, with PPro14, is that the range of "risky" somethings has been extended into a wide range of things which were previously always stable and trustworthy.  When in the history of ever has the Materials Room provoked app crashes?  It was always stable.  I just had a crash because I opened the Hierarchy Editor, for Tarim's sake.  Lost two hours of work.  Has the Hierarchy Editor ever, ever been unstable before?  This is getting to be worse than Poser 8 before the third SR made it stable for me.  Grumble.

I'm going to have to start running the autosave Python script again.  I hate to do that.  I don't quite trust Poser's Python callback functions.  I've seen weird things happen with those.  But it may be time for me to resort to that.  Sad, sad.  One wonders what they must be doing to poor Poser, to make it act up like this.  Are the Poser Team jabbing Poser with sharp objects, during development?  Giving it massive trauma and neurosis, I know not what?  It's acting like the freaky, traumatized chihuahua I once knew.  Every now and then it just has to go berserko, because its wires have been all crossed around and mixed up.  :unsure:

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.