Trimesh data is mostly just pointers to other blocks of data (look
up TQ3TriMeshData in the Quesa API reference). When you create a
new trimesh using an existing data set, you're just copying
pointers for the points, uvs, normals (etc). You're not actually
making a copy of the vertexes.
Great! I didn't understand which way it was. This way is much easier
to work with.
mem2 isn't a trimesh, it's trimesh *data* - GetHandle and GetData
are two totally different things. GetHandle returns a pointer to an
opaque TQ3GeometryObject (that's what you use to add it to a
display group) and GetData returns a copy of a TQ3TriMeshData
struct, but the actual vertex data is somewhere in the bowels of
Quesa, unless you made and assigned it yourself from scratch like
you do with the points above.
I understand that, I just thought that calling New Trimesh would
actually copy the data over creating new blocks for each data. If
that was the case, I thought there had to be someway to create the
trimesh object from an existing trimesh data so that it doesn't
copying the data.
Now that I understand how it works, I should be set now.
It works great!
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|