Here's the link to the site that made me finally understand quaternions today: http://iquilezles.org/www/articles/quaternions/quaternions.htm The data from the animations is in joint space as far as I can tell and not parent-relative, so you have transform (multiply) it with the bone matrix from the...

I've got the complete animation frame format now (all values in bone space and not premultiplied):

The animations should transform the existing bones for each frame. To play an animation, a program has to do the following: 1. Transform all vertices with the inverse bone matrix so the bones all equal the unit vector. (Noesis already does this, judging by the screenshots.) The mesh resulting from s...

You're right, I didn't notice that there was no "mass" parameter. The animations don't use Euler angles, at least not directly. I at some point had a program to output an animation where one bone's rotation values would increase at different speeds and the bone was rotating around the axes...

The only things that should matter for weapon attachments are the AttachPoint values in the body mesh. It's basically just another bone that marks the origin of the attached entity. The matching attachment point in the weapon mesh may be an additional transformation. I don't know anything about that...

Tamschi: For the drawcalls is it defined somewhere when I'm supposed to read bone indices? Some files don't have bones and so they skip that part. I'm thinking of looping through the entire file once listing all the sections and then seeing if there's a section 6 for bones in the file, but if it's ...

There's a Bone_Head in the body mesh too. I'm pretty sure you can just use the bones from the body mesh and only use the data from the attached mesh for the bone map.

It's the same with helmets and most armor. Weapons are attached to the AttachPoints from the text data instead.

Face 3065 is {3538, 3537, 3526}.

Wich one is it? I'll try to open it in MeshView.

It makes perfect sense if you only want to push the mesh to the GPU. Otherwise you'd have to rearrange the weights each time the mesh is loaded into the game.

If there is more than one draw call, the same bone id in the vertex weights can point to different bones. You really need to edit the weights to make it 100% compatible.

A bone id of 255 in the vertex weights means no bone, but the weight value isn't always 0.0 if the id is 255.

Tamschi, I'm having trouble understanding the function you sent to get the vertex weight, especially with the info about shaders. Couldn't I just get the vertex weight out of the vertex data? No, that won't work. The bone indices in the vertex data map to the bone slots in the draw call, not the bo...

I don't know if this works, but there are noesis.NOESISTEX_DXT1, noesis.NOESISTEX_DXT3 and noesis.NOESISTEX_DXT5 constants that you can use instead of noesis.NOESISTEX_RGBA32. The format should be somewhere in the DDS header. A few .tex files don't have reversed mip maps, so you have to check that f...

Here's some info on the animation frames that's currently not in the TQ.Animation.dll source: Basically, each frame is an array of 14 32bit floats. 0, 1, 2: Position offset vector. Default: {0, 0, 0} 3, 4, 5: These seem to rotate the bone. The bone changes size if you use more than one. Default: {0,...