Tesseract - Forum

#1 2014-09-13 16:56:40

gaya

Member

Arms animation

I noticed that the arms are separated from the weapons. Is there any documentation on how the weapon animations are synced with the arms animations? Or someone can point me into some code snippets that can give me some light?

#2 2014-09-25 01:02:00

Nieb

Administrator

Re: Arms animation

The arms & weapons were animated together, then exported to MD5 models separately.  Most of the "magic" is happening in the md5.cfg files, not code.

#3 2014-09-27 08:28:17

spikeymikey0196

Member

Re: Arms animation

The main question is why are we still using md5 files..

#4 2014-09-27 15:19:15

SniperGoth

Member

Re: Arms animation

Personally i thought that tesseract would be one of the first cube based games to make the .iqm the main model type.

#5 2014-09-27 19:23:34

spikeymikey0196

Member

Re: Arms animation

Ditto xD but i guess not.. Hardly any programs even support .md formats

#6 2014-09-27 23:53:29

gaya

Member

Re: Arms animation

It does support IQM, it's just not used by the default models.

#7 2014-09-28 01:28:30

Nieb

Administrator

Re: Arms animation

I used MD5 because 3dsMax doesn't currently have an IQM exporter.  There is a way to convert an exported FBX file to IQM, however I have not taken the time to tinker with it.  IQM doesn't do much different or better than MD5 so there isn't a pressing reason for me to pursue it.

#8 2014-09-28 02:02:15

ThaOneDon

Member

Re: Arms animation

Are you sure? It supports all this....

*little-endian binary format for fast loading
*supports variable vertex attribute formats including position, texture coordinates, normal, tangent, *blend weights, color, and custom attributes
*space-efficient quaternion animation encoding
*supports non-uniform joint scaling
*allows combined or separate mesh and animation files
*triangle adjacency data
*per-frame bounding boxes

#9 2014-09-28 20:01:30

Calinou

Moderator

Re: Arms animation

Are you sure? It supports all this....

*little-endian binary format for fast loading
*supports variable vertex attribute formats including position, texture coordinates, normal, tangent, *blend weights, color, and custom attributes
*space-efficient quaternion animation encoding
*supports non-uniform joint scaling
*allows combined or separate mesh and animation files
*triangle adjacency data
*per-frame bounding boxes

But we don't need any of this compared to MD5, technically. But unlike MD5, IQM is a maintained format – by the same developer as Tesseract.