Ok I have two rigs. i’m writting a script to post the animation from one to the other. The two rigs are the same but different joint placements as one is male and one female.
I’m just baking the animation from one to the other so I have calcualted the transform offsets from the female control to the male control. Then I’m setting a key every frame on the controls for the male. Now if I run the line of code for the setting the position of the object on each frame then it works and places the control with the expected offset from the females control. If I run the piece of code inside an At Time context with Animate On I don’t get the expected results but only on certain objects.
It looks like the objects that i’m having difficulty with are ones that have a parent object with a position constraint on them.
Any idea what is causing this? Anyone?
In closer investgation it isn’t the position constraint on the parent of the control that i’m getting the animation on but the position constraint on the parent of the objects I’m getting the animation from.
Also if I use sliderTime=t instead of at time t I get the results that I expect. I should note that using sliderTime is about 100 times slower then at time.
So what gives?
Hi Pen,
Just wondering if you resolved this problem. And also could I ask why you are writing your own code to transpose animation data from one rig to the another, rather than the stuff that ships with max for merging and retargeting motions. Sorry for being nosey !
Cheers
Dan
In Max 8 and 9 there is a memory leak in the save load animation tool. I can only batch about 30 files and it crashes Max. I need to do about 900 right away and then more after that. There should be a bug fix for this in the frist service pack for Max 9 and I could then use the save load animation tool. Also my system is about 300% faster then using save load as it only does what it has to. General tools often run into the problem of not being as fast because they are designed to work in many situations, if you can custom code for a specific situation you can increase the speed.
Oh and the way that I got it to work is I had to move the time slider instead of using the at time context. This is forcing an update to the matrix values, I might have another solution from Larry now that I have to try as well. Using sliderTime instead of at time has also slowed my code down so I want to find another solution if I can.
I see, I didnt know about the leak. Thanks for the info.
Cheer
Dan