Kritika Online animations (.anim)
Posted: Sat Aug 13, 2016 6:15 pm
I feel like I've almost gotten this figured out, but I'm hitting a wall.
The quaternion rotation data is stored as a int16[4], where the first three int16s are three encoded components (the encoding is simply mapping the range [0,65535] to [-0.707,0.707], and the fourth is a value from 0 to 3 which designates which component is missing (which I guess is necessary because unit quaternions can have at most a single component greater than 0.707, which is outside of the range of their serialized data format). So, for instance:
is the quaternion (0.0, 0.707, 0.0) with a missing fourth component of 0.707, recalculated during deserialization. Now I have the issue of not knowing which axes each of those fourth values maps to, which is an issue since the missing value also determines the mapping of the first three values. (I'm pretty sure 3 means the missing component is W, which logically would make 0, 1, 2 -> X, Y, Z, but beyond that it's guesswork.)
Complicating things further, setting all rotation data to (0.0, 0.0, 0.0, 1.0) (xyzw), aka no rotation, causes all bones in the model to become parallel ingame, which implies that bone rotations are actually stored relative to the parent bone's world rotation or something along those lines.
Luckily, there're a few animation files that exist that have a single frame in them, used for posing characters in dioramas. The sample I'm linking in particular has three files: the bones file, which contains the bind pose and all bones; the "_Freeze.anim" animation file, which has one rotation quat for each bone, starting at 0x2C22; and the camera animation file, which is for the camera panning around the diorama (you'd need to look at the translation data as well in this one).
The other good thing about this sample is that the bind pose here is actually pre-posed; that is to say, the animation data seems identical to the bind pose in the bones file, it's just stored differently. My knowledge of matrices and quaternions fails me here, though, especially when dealing with conversion to Blender's coordinate system and stuff.
Sample
Szkaradek123 posted an import script for Blender 2.49b in a previous thread, so that's a good reference for the bone format. Conveniently, the bone matrices are all stored in world space.
The quaternion rotation data is stored as a int16[4], where the first three int16s are three encoded components (the encoding is simply mapping the range [0,65535] to [-0.707,0.707], and the fourth is a value from 0 to 3 which designates which component is missing (which I guess is necessary because unit quaternions can have at most a single component greater than 0.707, which is outside of the range of their serialized data format). So, for instance:
Code: Select all
FF 7F FF FF FF 7F 03 00Complicating things further, setting all rotation data to (0.0, 0.0, 0.0, 1.0) (xyzw), aka no rotation, causes all bones in the model to become parallel ingame, which implies that bone rotations are actually stored relative to the parent bone's world rotation or something along those lines.
Luckily, there're a few animation files that exist that have a single frame in them, used for posing characters in dioramas. The sample I'm linking in particular has three files: the bones file, which contains the bind pose and all bones; the "_Freeze.anim" animation file, which has one rotation quat for each bone, starting at 0x2C22; and the camera animation file, which is for the camera panning around the diorama (you'd need to look at the translation data as well in this one).
The other good thing about this sample is that the bind pose here is actually pre-posed; that is to say, the animation data seems identical to the bind pose in the bones file, it's just stored differently. My knowledge of matrices and quaternions fails me here, though, especially when dealing with conversion to Blender's coordinate system and stuff.
Sample
Szkaradek123 posted an import script for Blender 2.49b in a previous thread, so that's a good reference for the bone format. Conveniently, the bone matrices are all stored in world space.