I tried to export a model as a 3d heirarchy into blitz3d yesterday and I couldn't find anly of the children objects. The Children objects were plainly visible in 3dc but blitz3d countchild() reported 1 and 3dc reported 4.
Did I screw something up? Could someone show me the proper way to save out a directx heirarchy that will be readable in blitz3d?
is the blitz command to find this information or is it used to find if any meshes have been loaded as a child of the mesh in question - did that make sense ?
in blitz you can " LoadMesh ( file$[,parent] ) " to make the new mesh a child of an already loaded parent - so countchildren(parent) should tell you if this has been done ?
I am not sure if countchildren() (in blitz) is to do with x heirarachy.
hope this makes sense and it is a guess - i have not tested any of this !
To me, this means that countchildren should return the number of children in a directx heirarchy. If I load the directx object in with LoadAnimMesh() then the heirarchy should be retained.
So I guess the question to ask now is whether or not the children - parent relationships in a directx object is refering soely to the heirarcy of the directx object? Or is it refering to something else?
If you have a look at loadmesh() it says about parents - so I thought that the countchildren() was for this ? If I get chance I will have a look tonight....
Thanks for that gakennedy. ("this was passed to me by Mark who wrote blitz" - name dropper ! )
I wonder if there is any speed or other benefit to using loadmesh() over loadanimmesh() - I guess there must be otherwise one would always use loadanimesh() ? (as I was saying to Bill Gates the other day )