I'm stumped, is there a simple explanation for what's gone wrong here? When I move a pose slider on one character it also changes another character.

Click to view attachment

I put the test prj in the WinkeGenericAdult folder if anyone wants to try it.

I didn't see the problem you were having. It may be from having the relationship window still open.

I guess I should have tried the old save-quit-and-restart. It seems to be gone now.

Well you may think it's gone - but it could come back. My guess is the model got corrupted in the process of making the poses, and you had a chor going that contained 1 or more instances of the model.

If you changed the model again and resaved it at one point - it might have fixed itself?

I had seen this very same behavior with the goose models about 1 year ago - before the model got fixed. (I had an A:M report on it)

I have also run into this repeatedly on just about all the models that I've ever textured for TWO (until I learned what was causing this). There seems to be some corruption of the model data that occurs if one is altering the model and at the same time has a chor open that contains more than 1 instance of the model being altered. Even sometimes if there is only 1 instance in the chor.

Somehow data from the chor gets written into the model data. The model gets corrupted with the instance data of the chor.

Most of the time it is not obvious that something is wrong until you bring up the model in another session of A:M. Your problem may appear to be gone because of the order in which you added the models to the chor (and then perhaps deleted them from the chor and re-added them).

For example in this A:M report

http://www.hash.com/reports/view.php?id=4170

I had 2 instances of the bear model in a chor at the same time that I was texturing him in the model window. They appeared to be working correctly in the chor. However, the next time I brought this model into A:M it's constraint targets were corrupted and pointed to a now non-existent 2nd instance of the bear model.

The work around that I have found is to never have an action, or chor open or active while texturing or altering the model, even if the chor only has 1 instance of the model.

If I saved it with no chor window open, and reopened it later and it seemed to work ok, is the problem gone for good?

Je ne sais pas.

I guess if it really looks like its ok then it probably is. If you've closed A:M, then re-opened it and brought in multiple instances into a new chor and the cross pose behavior is no longer there - then I GUESS ??? it's ok. Try adding 3 instances and see if the errant behavior shows up in any of them.