[request] use triangle strips, not triangle lists

With all the freely available stripifiers out there, it would be nice if the exporter took care of this for us. My test app is very slow, because the current engine uses 3x vertices than it should :'(

Th perfect strip that can be displayed In 1 call doesn't exists... Degenerating triangles is not an options and dealing with multiple vbo for every strip will penalize the performance. From my test it is alot more trivial to use indexed triangle lists optimized for vertex cache which is better and faster to render than strip... Do the test...

sio2interactive wrote:Degenerating triangles is not an option

Why? It worked well when I used that for an old project, using only one vertex array for the whole mesh.

There is a really good stripifier class in the powervr sdk. it's used in oolong so i guess it's opensource now.

Degenerating triangles is not an option when using physic... Normals may be inverted and you will also overload the physic calculation by using veryices on triangle mesh or convexhull that are mor necessary.

Ok I didn't think about the Physics

One idea: you could still use degenerate triangle strips for the rendering, and keep a list of the degenerate indices in a physics-specific array. This array would only serves the purpose of breaking the degenerate strip into multiple normal strips.

I can't even imagine how I would be able to handle soft body physic like that since the physic is applied on a per vertex basis and not the object... Recalculating this in real time is not even an option...