I am fiddling around with importing motion data from other (non-am) sources and am encounting some things that I am having trouble getting my head around.
Here's the setup:
(Using Version 12)
I've written a converter app that takes the source motion data and outputs an A:M .act file.
The model I am applying these actions to has 2 nulls (Marker1 and Marker2). The converter (which currently works with 2 'bones' until I get this sorted out better) outputs the motion data to one or both of these Nulls (it ignores any other data at the moment).
For the most part this works kind of OK but I've noticed some things and I can't quite get my head around yet:
Moving the NULLs in the model results in a corresponding change in relative position in the action file.
Changing the roll handle or orientation of the NULL in the model causes a corresponding shift in the 'hemisphere' of the action- i.e. if I rotate the NULL 90 degrees on the Y axis (from pointing straight ahead to pointing to the Right), in the action any Z movement is now X movement, etc.
The app I wrote outputs Position (XYZ) and Orientation (quaternion, XYZW) data.
Can someone explain in technical detail why changing the NULL position/orientation in the model file would change it in the action when I'm explicitly specifying those?
Are actions relative to something other than the main model bone?
Thanks in advance!