Quote -

You got THAT right! But I went full toot, did a disc check, defrag, virus scan, spybot and adware scan. I'm not paranoid, but something was killing me on this one program. Whatever it was, it seems to have cured itself partially in both P6 and P7. I still can't figure out the cause, which is my main concern now. I applied a BVH to V3 with some wild moves, using dynamic hair, and it all stayed in place! OK, one-for-one, so far.

Now if the 'Drop Figure to Floor' was a function built into the keyframe editor ....

Thanks a bunch for the replies from all whom responded.

JP

Glad your problem is fixed - I know it's not the first thing anyone would think to do, but strangely enough whenever I have stability problems or strange things showing up like this in Poser I've found a disk check followed by a defrag tends to fix the problem.  Weird, but effective :)

The cause, as near as I can tell, is crosslinked files or a heavily fragmented Windows virtual memory swap file.   Poser relies heavily on this swap file, because it is such a huge memory hog.  No matter how much ram you seem to have in your system, Poser always wants about 10 times more than that to do pretty much everything.

So if you get something crosslinked or jinked up in your virtual memory swap file, or it simply gets too fragemented to be read quickly enough, Poser starts to get - well, hinky to use the standard professional terminology of us programmer types.

In short the major contributing factor to problems like this are generally the fact that Posers memory management sucks - bad.   Again, apologies for the overwhelming use of technical terms in the explanation. :)

-Never fear, RenderDog is near!  Oh wait, is that a chew toy?  Yup. ok, nevermind.. go back to fearing...