Sorry your browser is not supported!

Ok starting with the question:
How does AppGameKit know when one child mesh ends and the next one begins when you use LoadObjectWithChildren to load a level?

I made a level in maya. It's a large mesh that acts as a terrain with a bunch of buildings, objects, foliage and trees scattered around it. Everything is textured, every object has it's own texture. NOW the issue is that if I export everything as one combined mesh then that means I'd have to also make a One texture file containing all the textures - Terrain ,Buildings, Foliage, Trees, etc. So the whole thing would get pretty damn big if I hope to keep any sort of discernible detail. BUT if I do that all the objects remain where they are precisely where I placed them in the model.

On the other hand I could export each object separately, which means I can have a separate texture file loaded for each one, BUT i"ll have to create a sort of level editor to position all objects, save and load system for that too (Which will happen, just not now).

The LoadObjectWithChildren is technically perfect, it loads objects as separate children and each child mesh can have a separate texture assigned to it. The issue is. How does AppGameKit know which meshes belong to which child? Can you group meshes or combine them? Combining kinda puts a big old nail on any further edits you wanna make to that object unless you do some duplication and saving shenanigans. If I have 3 things in my scene, One is the terrain (as one mesh) as well as an object #1 (made out of a cube, cone and a cylinder) and object #2 (made out of a sphere, a cone and a rectangle). Mind you none of these elements are combined so at any time I can grab the cylinder from Object #1 and move it next to the sphere of Objects #2 How would AppGameKit know what belongs to what child? Object grouping, Material Naming? Is there a way to predict or predetermine which mesh / object child is going to be which child id

Help Manual --> Home --> Commands --> 3D -->

GetObjectNumChildren( objID )

GetObjectNumMeshes( objID )

GetObjectMeshName( objID, meshIndex )

SetObjectMeshImage( objID, meshIndex, imageID, textureStage )



Looks like it is all bone based.

I'm guessing those separate meshes would be assigned to separate bones that are limbs.

Not my area of expertise (no area is ), so maybe the experts will join in the thread soon.

I think assimp will keep all meshes with the same texture in a group.
So if you want to add materials like I did in the lighting demo for the ShaderPack then you can seperate them via meshes/textures.
Maybe you can predict the meshes with the texture order inside the object file

Ah, I see so the child system is mainly for rigged objects. Looks like I gotta make a level editor anyways.