Milkshape (ms3d) AnimatedNode -> very slow

Thorben Linneweber · Post by **Thorben Linneweber** » Fri Oct 14, 2005 1:39 pm

okay, 5k (4990) frames for the body and i think 500 for the legs

I need this number of frames to show even more complex movements... (jumping, crouching, throwing nades, shooting with different guns...)

(look here for 2 screenshots:
http://teamoperations.blogspot.com/ )

I already completed the player class and it works really fine... only the speed of 20 players sucks...

Is there a possibility of reducing the quality of the mesh in milkshape?

>> if you'r hardware isnt drastically better than mine you really should concider using LOD or simmilar stuf..

Is this possible in Irrlicht?

ThommyE · Post by **ThommyE** » Fri Oct 14, 2005 2:41 pm

i was not talking about the frames... i talked about the triangles.. you grafic card may simply be not able to render all this stuff fast enough
EDIT: I icq-ed you..

pfo · Post by **pfo** » Fri Oct 14, 2005 8:56 pm

The problem is perhaps also caused or influenced by the MS3D loader, which creates 3 vertices per triangle and does not take advantage of reusing vertices in the index buffer.

Are you sure about that? I use ms3d models to build collision geometry, and the vertex_count / 3 != index_count, which tells me that it is reusing vertices, in fact the index count to vertex count relates directly to what ms3d tells me it is. I'll have to doublecheck that and get your patch if you're correct, that would be great to catch that now before I start adding many many models to the game and wonder later how I could squeeze some bandwidth.

Andi|xng · Post by **Andi|xng** » Sat Oct 15, 2005 8:55 am

pfo wrote:Are you sure about that? I use ms3d models to build collision geometry, and the vertex_count / 3 != index_count, which tells me that it is reusing vertices, in fact the index count to vertex count relates directly to what ms3d tells me it is.

I don't understand your calculation "vertex_count / 3 != index_count". I never saw a model that has more vertexes than indices

That would mean that many vertices are not used at all!

Just download my patch and compare the new vertex/index-creating loop with the commented old one. You can see, that the old one (commented) creates really a new vertex for each index.

Example for my test model: Old routine: Created about 3000 vertices. New routine: Creates only about 1000 vertices.