I have a few options for "next steps" including:
* Figure out bounding boxes using meshes
* Move it into a plugin for re-usability
* Build scene from meshes/nodes for more flexibility
* Move on to something completely different (audio inspector)
I'm inclined to go to audio inspector and then come back to the
mesh/node scene builder.
Animation API is good but incomplete.
Cannot find animations related to an entity which means multiple
animations would likely break this flow.
With more precise asset control of Animations + Entities it would be
fine, like in the example, but not "Load the GLTF and figure it out in
the code" like I'm trying to do.
The gotcha was that the 3d camera was rendering the UI but shouldn't
have.
Now I think we can show the previews.
Still not sure how to render each preview in it's own "space" without
them overlapping...
It has the basics of a GLTF inspector, in that it gltf files and you
can inspect a scene... but only the first scene.
Need to add more functionality like previews and selection.
Each scene has it's own camera and light, so we can trivially (fingers
crossed) preview those with a render target of image and then pipe that
to a UI element.
That will happen... tomorrow.
Elijah Voigt