I've tested the "export .X as animation" option within Blender, and then the scene is exported with frame-sections.
I created a scene with one cube as parent, with 2 children (a sphere and another cube).
When I load that scene into B3D (loadanimmesh), only the parent is visible and the scene only has 1 child.
The other cube and sphere are not visible and don't appear to be children of that parent cube.
However, the meshes are present in the .X file.
I tried printing the number of children of that parent cube, but there are none.
Seems that Blender's .X export doesn't work perfectly.
But no problem, my game will use one big datafile, which declares all waretypes, missiletypes, shieldtypes, shiptypes, stationtypes, ... in the game.
I'll just add a section in those station-types which will declare the positions where the weapons should be mounted.
Then I can also add a few lines which state which weapons should be installed there.
Then I can add them via code.
It was easier to have pivots in the .X file, which would be used as coordinates for the weapons, but this is no real problem.
The use for one big datafile, is just for modding purposes.
This way, a modder can add a new file (with other prices, new stations, new ships, ..., let the game use that new file and the game adapts automatically to the mod, including those adaptations in the game.
The game is only in the very early stages and I'm still learning a lot about modelling, texturing, ...
So the game will not be ready for the next few months/years.
I created a scene with one cube as parent, with 2 children (a sphere and another cube).
When I load that scene into B3D (loadanimmesh), only the parent is visible and the scene only has 1 child.
The other cube and sphere are not visible and don't appear to be children of that parent cube.
However, the meshes are present in the .X file.
I tried printing the number of children of that parent cube, but there are none.
Seems that Blender's .X export doesn't work perfectly.
But no problem, my game will use one big datafile, which declares all waretypes, missiletypes, shieldtypes, shiptypes, stationtypes, ... in the game.
I'll just add a section in those station-types which will declare the positions where the weapons should be mounted.
Then I can also add a few lines which state which weapons should be installed there.
Then I can add them via code.
It was easier to have pivots in the .X file, which would be used as coordinates for the weapons, but this is no real problem.
The use for one big datafile, is just for modding purposes.
This way, a modder can add a new file (with other prices, new stations, new ships, ..., let the game use that new file and the game adapts automatically to the mod, including those adaptations in the game.
The game is only in the very early stages and I'm still learning a lot about modelling, texturing, ...
So the game will not be ready for the next few months/years.