Saber model - vertex limit in glm and in MD3

[Langerd]

What is the maximum count of the glm vertex count and MD3 ? I know that if you want create MD3 as the moving enity it must be lower than 1000 vertexes ( The Lambda Shuttle MD3 model shows in Mrwonko's MD3 viewer above 1000 verts) but what about glm? The bug with the - ,,Run out of transform space " is caused by too many vertexes or something diffrent?

[Ramikad]

As far as I know the glm limit is also 1000 vertex per mesh, for a total of 32 max meshes in the same model. But I could be wrong.

[ensiform]

1000 is the maximum amount of vertexes that can be passed to the tesselator backend of the renderer. Technically the limit is 999 as the last one is reserved for internal use.

[Lancelot]

1000 is the maximum amount of vertexes that can be passed to the tesselator backend of the renderer. Technically the limit is 999 as the last one is reserved for internal use.

Maybe it's a stupid question, but isn't it possible to increase the vertex limit by modifying the source code?

[ensiform]

Sure but we're not going to in OpenJK if that's what you are wondering.

[minilogoguy18]

It doesn't need to be any higher anyway, a good modeler can use just as few as the source models and make it look good. Newer games don't really have much higher limits either, just using more complex rendering techniques that include displacement maps.

 

I'd keep it under 500 per object to avoid errors, going close to the top can cause problems when you have a base folder full of models that do the same thing, that's where the transform space error comes from.

[Lancelot]

Sure but we're not going to in OpenJK if that's what you are wondering.

It was a general question and not related to OpenJK.

 

Would be great if someone could actually increase the vertex limit.

It could open many possibilities.

[ensiform]

It applies to all surfaces not just models, and in order for the limit to be increased fully you must change q3map2 as well.