You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my project, i need to generate voxel meshes at runtime, which need collision. Those meshes are a regular 3d grid (surface-nets). Ive benchmarked the default TriangleSplitterBinning with the default MeshShape logic, and that one is a bit too slow. Ive modified the code to use TriangleSplitterMean, and that makes the generation significantly faster for the kinds of meshes i generate (my triangles are all almost the same size due to being a grid, so binning by centroid gives optimal results).
The thing is, there is no option or property to switch the binning logic. On my version of the library for the project, ive directly modified the code on MeshShape.cpp to use the other splitter, but thats only to test the others.
Is there a plan to add something to MeshShapeSettings or MeshShape constructor that would allow this sort of customized build logic? Or a known way to side-step this.
The text was updated successfully, but these errors were encountered:
I can add a setting for it. I've been tempted many times to just delete those other splitters (as they're inferior) but this is indeed a good use case.
In my project, i need to generate voxel meshes at runtime, which need collision. Those meshes are a regular 3d grid (surface-nets). Ive benchmarked the default TriangleSplitterBinning with the default MeshShape logic, and that one is a bit too slow. Ive modified the code to use TriangleSplitterMean, and that makes the generation significantly faster for the kinds of meshes i generate (my triangles are all almost the same size due to being a grid, so binning by centroid gives optimal results).
The thing is, there is no option or property to switch the binning logic. On my version of the library for the project, ive directly modified the code on MeshShape.cpp to use the other splitter, but thats only to test the others.
Is there a plan to add something to MeshShapeSettings or MeshShape constructor that would allow this sort of customized build logic? Or a known way to side-step this.
The text was updated successfully, but these errors were encountered: