Frame body {
FrameTransformMatrix {
1.278853,0.000000,-0.000000,0.000000,0.000000,0.000000,1.123165,0.000000,0.000000,-1.470235,0.000000,0.000000,0.135977,2.027985,133.967667,1.000000;;
}
Frame {
FrameTransformMatrix {
1.000000,-0.000000,-0.000000,0.000000,-0.000000,1.000000,0.000000,0.000000,-0.000000,0.000000,1.000000,0.000000,-0.142114,0.000023,-49.556850,1.000000;;
}
Mesh {
the entire mesh data is listed here <-----
It looks to me that the Tiny has only one mesh and the frame Frame should be the one that its pMeshConatiner points at the mesh data.
The rest of the frames would have their pMeshConatiner set to NULL after [font="TimesNewRomanPSMT"]D3DXLoadMeshHierarchyFromX is executed.
SetupBoneMatrixPointers is where I am stumbled upon.
[font="CourierNewPSMT"][font="CourierNewPSMT"]SetupBoneMatrixPointers(DerivedFrame bone)
{
if (bone->pMeshContainer != NULL)
//create an array of pointers[font="Monospace821BT-Roman"][size="1"][font="Monospace821BT-Roman"][size="1"]
[/font][/font]
if (bone->pFrameSibling != NULL) SetupBoneMatrixPointers( bone->pFrameSibling) ;
if (bone->pFrameChild != NULL) SetupBoneMatrixPointers( bone->pFrameChild);
}
Don't understand why SetupBoneMatrixPointers is set up as a recursive function. As mentioned above, the bone sibling and child should have no mesh data to point to, based on how the mesh data was set up in the Tiny.x file.
[/font][/font][/font]