The SIMPLE_INDEXED_MESH_MANAGER is a very old piece of code, but still viable for reasons you stated. It is missing information that can be used for texture mapping and color strips/fans, but it is rather memory efficient. I would access this mesh by wrapping the mesh manager, then expose the data through a public method or attach the mesh to the FACE. Since you whould facet the whole body in one API call, accessing the mesh through attributes on th FACEs may be easier. Try the following...
class MY_MESH_MANAGER : public SIMPLE_INDEXED_MESH_MANAGER
{
public:
virtual void end_mesh_output( ENTITY *entity, ENTITY *app_ref, ENTITY *format)
{
SIMPLE_INDEXED_MESH_MANAGER::end_mesh_output( entity, app_ref, format );
if ( mesh )
{
af_update( entity, MY_MESH_APP_ID, MY_MESH_USER_ID, mesh );
}
}
};
Then access the data as follows...
MESH * face_mesh = NULL;
af_query( (ENTITY*)face, MY_MESH_APP_ID, MY_MESH_USER_ID, face_mesh );
if ( face_mesh != NULL )
{
SIMPLE_INDEXED_MESH * mesh = (SIMPLE_INDEXED_MESH*) face_mesh;
// For every facet (or polygon) ...
for ( int polygon_index = 0; polygon_index < mesh->get_npoly(); polygon_index++ )
{
for ( int polynode_index = 0; polynode_index < mesh->get_npolynode( polygon_index ); polynode_index++ )
{
const SPAposition & pos = mesh->get_position( mesh->get_polynode( polygon_index, polynode_index ) );
}
}
}
What you may need is your own mesh manager. You could store data as floats instead of doubles, store exactly what you need as you want it stored, or feed data directly to your renderer, or whatever. Please watch this posting, and I will try to reply with a sample mesh manager you can use and modify to your liking.
