code:

    int          m_iNumPolygons;    CPolygon    *m_cPolygons;    int          m_iNumVertices;    CVector     *m_cVertices;    CVector     *m_cVNormals;    D3DMATRIX    m_tMatrix;    CVector      m_cPosition;    CVector      m_cAngle;    CTextureCoord *m_cTextureCoords;    CColor      *m_cVertexColors;    int          m_iTextureType;    int          m_iShadingType;

Greetings Tobias

[This message has been edited by Ake (edited October 04, 1999).]

WSG_XYZ
WSG_COLORn (0-15)
WSG_TEXCOORDn (0-15)
WSG_NORMAL

In addition, the PrimitiveSet has a few functions like ImmediatePrimitive() and
IndexedPrimitive() for specifying TRIANGLES, TRIANGLE_STRIPS, TRIANGLE_FANS etc.

Each PrimitiveSet is bound to a "shader" script, which determines which textures will be used, blending setup between texture layers and what texture coordinate channels to bind the images to. Etc etc.

I find this approach much more flexible than having a fixed class of a "3d" object, as each Geometry-based object has a more "API" based relation to the graphics engine.
YMMV.

for a single stream the setup would be something like the following.(complete objects have 1 or more streams)

Surface* // specs textures/blends/procedural // functions
polytype // particles/tris/bezier patches
indices* // index array
verts* // vertex array
texverts** // pointer to texture coord arrays
// the number used is determined
// by the surface
normals* // normal array

I'm writing a simple geometry engine in c++ to work on top of OpenGL. As I began to lay down some code for the 3DObject class I was wondering if anyone had any experience writing one already and could give some ointers or even a sample class definition. e.g. something like the following ....

class C3DObject : CWorldObject
{
public:
C3DObject();
virtual ~C3DObject();

float* m_pfVertices;
unsigned int m_uiNumVertices;

float* m_pfNormals;
unsigned int m_uiNumNormals;

float* m_pfColours;
unsigned int m_uiNumColours;
};