This is not true for the Editor importer, since they are calculated in a post-step via mesh.RecalculateBounds();.
Users might run RecalculateBounds manually at runtime as well, but I'm wondering if doing bounds calculation during positional data extraction yields better performance.
Resulting meshes have invalid bounds currently.
This is not true for the Editor importer, since they are calculated in a post-step via
mesh.RecalculateBounds();
.Users might run
RecalculateBounds
manually at runtime as well, but I'm wondering if doing bounds calculation during positional data extraction yields better performance.