Anim8or Community

Thanks I do not know if will help, but I am trying to convert euler angles to anim8or relative to bone. Not sure how bvh stored them, but I'm having problems in the final step, which is mapping euler angles to instead axis-angles of the bone XYZ.  How perfect did you get that conversion going?  (Maybe bvh isn't stored that way, as euler).

Sorry I was gone for a week, thanks for the reply!  I'm trying to go from FBX format into anim8or format.  It seems like XYZ euler angles in FBX.  I sort of deduced similar to what you had, but I'm getting lost in getting from my euler, adjusted to the relative to parent bone.  Not sure if you have done something similar and have at least pseudocode on how to do the conversion?   I can't figure out the math to go from my euler, such as 15, 30, 45, to an euler relative to parent bone.  Please help!  Maybe assuming have parent's bone quaternion, and your XYZ euler relative to parent, how to go to anim8or XYZ.

I was able to get the skeleton fine translated, it's just the keyframe angles themselves that won't translate.  I made a 0 sized node, which matched the way I had the FBX, in between bones, and those were used for rotations.  I believe the issue is just translating rotations properly.

Here's my attempt at least...
FBX: http://goldeneyevault.com/priv/an8conversionattempt/animation.fbx
An8 (skeleton nodes):
FBX: http://goldeneyevault.com/priv/an8conversionattempt/animation.an8

I may have requested this before, but I can't remember if I actually posted or not, but anim8or really needs vertex colors.  That would really be great.  I guess some sort of painting tool with it.

Sounds good, thanks for feedback!

Oops I forgot I already posted about greyscale with a sample, sorry. http://www.anim8or.com/smf/index.php/topic,4778.msg34733.html#msg34733

The environment mapping was spherical yeah, but sounds like you knew about it.

For line lengths and screen coords, was CAD drawing mode lines, not mesh. : http://i.gyazo.com/1926408c79ab5adebee64cf0f70210d1.png

If too much on screen for showing line lengths, maybe just show the length for the one you clicked in status bar for now?

Also (per same pic), the bottom right has a positive number, top right had a negative number, of which there should have only been a negative number if it were using world coords because the line started at 0,0,0, so I think the coords are screen not world.

Does it use the same orientation as the bone's orientation (ie. relative to its parent?)?  So it's like, taking the normal XYZ axis, rotating to bone orientation, then rotating euler from that?  For my part 14, what did that equate to, for the XYZ directions?

To go from absolute euler, I suppose you need to, rotate the rotations by the rotation from axis to bone orientation...I think

It doesn't appear to be euler angles, at least, not the axes I'm using.  Here is my sample file. 

I am setting a "leaf" part, at a joint "bone" 14, to 90,90,0.0.    In order to make it match what it should be, you would need to set -90,90,0.  But there's not a simple pattern. 

It should look like "expected.png".  It results in anim8orresult.png.  Also, weird, for that same part 14, is that (anim8or angles only) 90,90,90 is equal in anim8or to 0,0,90, which shouldn't be true if euler.  If it were true euler, this would not be true. 


Below are my tests of correct euler, vs anim8or.
Expected    Anim8or needed to match
90,-90,0    90,90,0
-90,90,0    -90,-90,0
90,90,0     -90,90,0
-90,-90,0    90,-90,0
 
90,0,-90     90,0,-90
-90,0,90     90,0,90
90,0,90     -90,0,90
-90,0,-90   -90,0,-90

0,0,90       90,90,90   0,0,90

You can also see, that the FBX file (imported into a tool, such as XSI), with those rotations matches my picture...so anim8or isn't straight euler.

Anipov tool, open source, does not convert the rotations properly either to milkshape format, even when "fixed" in anim8or.    So this doesn't seem well known unfortunately.

I'm trying to convert some animation data into .an8 format, for use by anim8or.  My original data is stored in euler angles, where you rotation each joint by X, then Y, then Z.

Unfortunately, setting anim8or rotations for a joint angle to that, doesn't get the correct rotation.  How are anim8or rotations stored for joint angles, and how do I convert it? 

For example, euler angles of 0 X, 90 Y, 90 Z do not yield correct rotations in anim8or.  Below yields the wrong ones. 

jointangle { "11-13" "X"
    track {
      floatkey { 0 0 0 0 "C" }
      floatkey { 15 0 0 0 "C" }
      floatkey { 54 0 0 0 "C" }
      floatkey { 67 0 0 0 "C" }
      floatkey { 89 0 0 0 "C" }
    }
  }
  jointangle { "11-13" "Y"
    track {
      floatkey { 0 90 0 0 "C" }
      floatkey { 15 90 0 0 "C" }
      floatkey { 54 90 0 0 "C" }
      floatkey { 67 90 0 0 "C" }
      floatkey { 89 90 0 0 "C" }
    }
  }
  jointangle { "11-13" "Z"
    track {
      floatkey { 0 90 0 0 "C" }
      floatkey { 15 90 0 0 "C" }
      floatkey { 54 90 0 0 "C" }
      floatkey { 67 90 0 0 "C" }
      floatkey { 89 90 0 0 "C" }
    }
  }

My bone structure, is composed of 0 sized joints, and bones connecting each 0 length joint, and all rotations are around just joints.

Using these axes in my source data: