Handling mesh resources

Started by
0 comments, last by MikeyO 19 years, 2 months ago
I've written a class that handles meshes, their materials/textures/etc, and I originally was planning on having all the objects that use the same mesh to share the same reference (to the mesh object), but then I got to thinking about LOD with a progressive mesh, and I'm wondering what the trade-offs would be and what people would recommend when it comes to LOD and progressive meshes and sharing resources. Should I just have each object load it's own mesh and update its vertices/position every time it reaches a new distance (say based on 10's or 100's units from the camera) or have it dynamically change the number of vertices based on how far away it is from the camera that particular frame (And share the same Mesh reference)? Or is there some completely better way that I'm not thinking of? What has worked for you in the past, or what would you recommend?
Advertisement
*cough*

Anybody?

Nobody knows how fast changing the vertices in a progressive mesh is?

This topic is closed to new replies.

Advertisement