forge-scene-model-loading

To load and render glTF 3D models in an SDL-based project, process the glTF assets through an asset pipeline to generate .fscene, .fmesh, and .fmat files, then use forge_scene_load_model() to handle file loading, GPU buffer upload, and texture binding automatically via ForgeScene.

The ForgeScene pipeline format for 3D model loading consists of .fscene, .fmesh, and .fmat files generated from glTF-derived assets, containing scene hierarchy data, mesh geometry, and per-submesh materials with textures alongside them for straightforward rendering.

Yes, you must use an asset pipeline to process glTF models and generate the required .fscene, .fmesh, and .fmat files, copying textures alongside them before ForgeScene can load and render the 3D models.

forge_scene_load_model fails to render 3D model textures if the asset pipeline did not copy the texture files alongside the generated .fscene, .fmesh, and .fmat assets, as the loader requires per-material texture paths to resolve correctly.

Yes, ForgeScene renders complex 3D scenes by traversing the scene hierarchy and binding per-submesh materials, supporting instanced meshes and enabling straightforward display of pipeline-processed assets in SDL-based projects.