I am quite confused on how the new render system and dots handles procedural mesh generation, since the RenderMeshArray is per entity chunk,
and every single mesh will be unique and runtime generated based on some paremeters and external inputs. Those parameters are dynamic at runtime, and will be updated quite often.
Are there any docs, samples, examples of generating Many™ meshes procedurally and runtime? Do I really need to mantain game objects , or use Graphics.DrawMesh manually?
You can register meshes directly with EntitiesGraphicsSystem and assign the index that gives you to MaterialMeshInfo. The resulting MaterialMeshInfo will ignore the RenderMeshArray and use this custom mesh instead, and then you can animate that mesh.
Do you have an updated simple example? I checked out your project on github and tried to use your framework. I was very hopeful it would work for me. I was trying to use your Dynamic Meshes example, but it didn’t work with the latest version of your framework (7.4) and Entities Graphics 1.0.11. Ideally I would like to see an example outside your framework that shows how to register meshes directly with the EntitiesGraphicsSystem. I have attempted to copy the mesh and materials from the Shared RenderMeshArray into a new RenderMeshArray, but saw the same massive performance hit when changing the vertices of the mesh.
I’ll update the guide to not use obsolete baker APIs. But the example code is working for me right now. I’m willing to investigate the issue you encountered if you provide more info.
I wrote my framework partly to bypass performance problems like this. You will need to find an answer from someone else.