model formats

[Crava_Loft]

I think with the release of wolfenstein enemy territory it shouldn't be hard to port its model loading code to tremulous.
(it is also stable)
If the modelers still have the model source files it would take a little work to export them in w:et format

There is also a second option: http://lee.fov120.com/iqm/
This provides a complete tool chain

[gimhael]

The wolfenstein code was released under GPLv3, so if you want to incorporate some Wolfenstein code into Tremulous, Tremulous has to switch to GPLv3 too.

I thought about IQM support in Tremulous, the format is a lot simpler than MD5 and the renderer code for loading / rendering a model should be pretty easy. With the current animation system you could only switch between the poses stored in the file, for control of individual bones you'd need a new cgame api.

[Crava_Loft]

You look at it from the wrong side. Be positive. Don't worry, no one will ever change the model format, no matter what. You don't need to list the obvious obstacles.

[gimhael]

Work in progress:



(The scale of the example IQM model is much smaller than the usual trem models)

The whole model can be animated as usual, but animating individual bones is not implemented, because that would require a new API.

PS: this model cannot be rendered in a standard tremulous client because it also breaks the infamous 1000 vertex limit.

[Fox One]

PS: this model cannot be rendered in a standard tremulous client because it also breaks the infamous 1000 vertex limit.

There is, of course, a way around the vertex limit. I know for a fact that this method works in Blender. All you have to do is split up your mesh, assuming it is a single Object that you would be exporting as a single .md3 file. If you select a section of the mesh of your single object and split it into another object (press P after selecting an area), each object can contain up to 1000 vertices. Multiple objects can be exported as a single .md3, as long as you select all of them at the same time before running the exporter.

[gimhael]

I'm not sure that you can split an IQM model into multiple objects without disrupting the bone hierarchy, but as you can see from the screenshot, the vertex limit can also be lifted by changing the renderer.

[Crava_Loft]

bump the limit. it is stupidly low anyway.
you can also split the models and use the tag system to join them back. but it is stupid.
one of the main points of using a skeletal model is getting rid of segmented models. thus giving you more realism.

anyway it is a good start