head_root rotation doesn`t fit to the facemarkers
Posted: Sun Jun 27, 2010 3:28 pm
hi,
we`re using arena expression 2.6, after cleaning and trajectorizing the data seemed pretty good to use it for the characters face,but back in max or motionbuilder, when importing the data (FBX-format) the headrotation doesn`t seem to fit to the movement and rotation of the markers, so the face doesn`t get along with head. first there is always a delay and the second thing is the more the head rotates to one side the less the markers rotate.
the problem is just there when loading the data (see pics
http://img208.imageshack.us/img208/3934/11138014.jpg delay problem, notice the data is fresh imported i only constrainted a box to the head_root_bone
http://img36.imageshack.us/img36/4605/r ... rinzip.jpg rotation problem, i worked with position and orientation constraints to link the markers to the bones, never mind the skining atm)
can`t figure out whats the reason for this,
is it an fbx issue, is it a mistake done in the cleaning or trajectorize process, are there any buttons or properties for handling this?
the only thing i know the data can be distorted by linking or rotating the optical data in a wrong way
we`re using arena expression 2.6, after cleaning and trajectorizing the data seemed pretty good to use it for the characters face,but back in max or motionbuilder, when importing the data (FBX-format) the headrotation doesn`t seem to fit to the movement and rotation of the markers, so the face doesn`t get along with head. first there is always a delay and the second thing is the more the head rotates to one side the less the markers rotate.
the problem is just there when loading the data (see pics
http://img208.imageshack.us/img208/3934/11138014.jpg delay problem, notice the data is fresh imported i only constrainted a box to the head_root_bone
http://img36.imageshack.us/img36/4605/r ... rinzip.jpg rotation problem, i worked with position and orientation constraints to link the markers to the bones, never mind the skining atm)
can`t figure out whats the reason for this,
is it an fbx issue, is it a mistake done in the cleaning or trajectorize process, are there any buttons or properties for handling this?
the only thing i know the data can be distorted by linking or rotating the optical data in a wrong way