Blender, Collada, Multiple Meshes
by Gary Hoffmann · in Torque 3D Professional · 07/09/2009 (8:50 am) · 1 replies
I’m trying to figure out how to get multiple meshes under a single detail level (I see this mentioned all the time as the way around the 10k limit) in Blender with Collada.
Now, I can create a model and setup the nodes to appropriately export (with Collada) with multiple detail levels, etc. as long as I only have one mesh per detail level. The problem is that the object node (which is the parent of the mesh node) has to be named for the detail, like “Shape100” or “Shape32”. Unfortunately, in Blender it isn’t possible to have multiple mesh nodes under a single object node. You can have multiple vertex groups but they will all still be considered a single mesh node.
I’ve tried making a second object a child of my shape object, so that I would have the Shape object node with a child of a mesh and a second object node which has a child of a second mesh, but the collada importer ignores the child object altogether and just uses the mesh directly off of the shape object only.
Is this even possible?
Now, I can create a model and setup the nodes to appropriately export (with Collada) with multiple detail levels, etc. as long as I only have one mesh per detail level. The problem is that the object node (which is the parent of the mesh node) has to be named for the detail, like “Shape100” or “Shape32”. Unfortunately, in Blender it isn’t possible to have multiple mesh nodes under a single object node. You can have multiple vertex groups but they will all still be considered a single mesh node.
I’ve tried making a second object a child of my shape object, so that I would have the Shape object node with a child of a mesh and a second object node which has a child of a second mesh, but the collada importer ignores the child object altogether and just uses the mesh directly off of the shape object only.
Is this even possible?
About the author
Torque 3D Owner Gary Hoffmann
For anyone’s future reference, there are two cases and each needs to be handled differently.
For the object node that is a child of the start node, your second object should be a child of this object node with a different name but the same detail number at the end.
For other object nodes you should *not* make it a child node of anything, simply name it a different name with the same detail number at the end.