Ahh ok makes better understanding now. So let me rephrase to see if I grasp it.
So to be able to go back and say move a "mesh" loaded object it has to have a unique identifier hense the TriMeshObject(HC) needed. Now if it's a static land mass that 's not going anywhere in the future is there a need for this or is it just better coding to go ahead and plop it in.
Also question for you all, now that I got something of land masses ploped around, would you recommend using TYPES so that I can pass through a routine to hide and show land meshes based on if they are seen by the camera, hense a cheap LOD style of code.? or can I still cycle thru the Meshes with a simple For Next loop.addressing the LandMesh(HC) and or TriMeshObject(HC).
Again thanks for the input, it's slowly getting there.
Topknot ;)
So to be able to go back and say move a "mesh" loaded object it has to have a unique identifier hense the TriMeshObject(HC) needed. Now if it's a static land mass that 's not going anywhere in the future is there a need for this or is it just better coding to go ahead and plop it in.
Also question for you all, now that I got something of land masses ploped around, would you recommend using TYPES so that I can pass through a routine to hide and show land meshes based on if they are seen by the camera, hense a cheap LOD style of code.? or can I still cycle thru the Meshes with a simple For Next loop.addressing the LandMesh(HC) and or TriMeshObject(HC).
Again thanks for the input, it's slowly getting there.
Topknot ;)