Collision mesh hierarchy

We're working on getting ragdoll physics working on a quadraped over here. The quadraped DTS and DSQ files have been exporting and working great for weeks now. Now to get the ragdoll stuff working, I've created a collision mesh for most of the bones, and made them children of the bones they represent. Here's a bit of the schematic and some visualizations:


So far so good. Now when I get this into ShowTool, I can see that the hierarchy looks a little different than I expect:


The problem here is that Max is exporting an additional non-mesh node for each of the convex collision meshes that we're intending to use for our ragdoll. What we need is for the convex mesh to be a child of the actual skeleton's nodes instead of this new node. In the image above, we need:

The convex mesh Convex_Trike_LFShoulder ("Convex Mesh" in RED box) to be under the *node* Trike_LF_Elbow ("Regular Skeleton Node" in GREEN box) rather than under the *node* Convex_Trike_LFShoulder ("Convex Mesh Node" in RED box).

Ideally, we'd also be able to do away with the Convex_* nodes altogether, since they also screw up the parentage hierarchy between nodes. Here is an mockup image of ideally how we need the hierarchy to be:


A secondary, but much less important issue is that Max is also exporting the convex meshes it uses to show the bones in Max (the RED box, "Max Skeleton Mesh"). If there's a way to get rid of this behavior, it'd be handy to do, but the above issue is the main problem and really somewhat of a show-stopper compared to secondary problem.