On rewriting the Mesh Object in gl3ds i come to a question that i do not know to answer:

Should i use a TFace Structure in it or not (In the latest released version of gl3ds i have both and that is bad!):

TFace
--VertexIdx 1..3
--NormalIdx 1..3

array of TFace

vs

array of VertexIndices
array of normalIndices

So the real question is: is there a one on one relation between normalindices and vertexindices?
Second: Does TFace make things more complicated or easier?
Third question: how can the texture coords u and v be implemented into TFace or should i leave them outsite and use vertexidx to get the right ones.

Do let me know so i can improve that part (for now i commented out TFace and rewrote a few lines that used it).

_________________
http://3das.noeska.com - create adventure games without programming

In my opinion:

PVertex = ^TVertex;
TVertex = record
Position: PVector3f //the vectors are defined in a separate array. So it is easy to delete them.
Normal: PVector3f; //..
TexCoord: PVector2f; //..
end;

TPolygon = record
Vertexes: array[0..2] of TVertex;
end;

and then you have an array of TPolygon.

My structure, which is in a way similar to your Face structure, would make the hole thing much easier to understand.
It has the advantage that you have all the information of a Vertex in one record.

_________________
bester uo-shard: www.uosigena.de

This structure i prefer, because its optimised for vbo.
The each array in TMesh get a own VBO and the Mesh is sorted by Materials, so you can call the Materialscript and can handle Face specific rendering(alpha, shader variables,...).
The TFace get a extra Normal array for stuff like Physic. This normal is not smoothed.
A simular structure you will find in Blender.
I hope it will help you.

_________________
"Wer die Freiheit aufgibt um Sicherheit zu gewinnen, der wird am Ende beides verlieren"
Benjamin Franklin

Projekte: https://github.com/tak2004