I am thinking about changes to the Blender exporter centering around generating more optimized objects before they are even loaded. Am using this for my planning guide, https://doc.babylonjs.com/how_to/optimizing_your_scene
Some of these features are scene wide, like freezing active meshes. Probably not going to do those. Those are best controlled with your own code.
Some I am already doing, like FreezeWorldMatrix, and probably will put in the CSV statistics output file, making it optional.
I do have questions about some others. First, I have a ‘check only once’ option for a material. It never did what I intended. Can you freeze a material, possibly before the texture has even arrived? If yes, can this be specified in the JSON file?
Next, do meshes without indices have to be converted, or can they just be created that way to begin with? If yes, I could do a custom property on a mesh by mesh basis, but think specifying a reuse threshold and let the system decide would be more powerful. Would be a little slower, since would have to generate the indexed version first in order to decide if the threshold was crossed, then maybe redo it again without the index, but so what.