Decals: Add support for rigged meshes + optimization for speed #13111
Conversation
|
Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s). |
|
Fix #13084 |
|
Snapshot stored with reference name: Test environment: To test a playground add it to the URL, for example: https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13111/merge/index.html#WGZLGJ#4600 Links to test babylon tools with this snapshot: https://playground.babylonjs.com/?snapshot=refs/pull/13111/merge To test the snapshot in the playground with a playground ID add it after the snapshot query string: https://playground.babylonjs.com/?snapshot=refs/pull/13111/merge#BCU1XR#0 |
Decals: Add support for rigged meshes + optimization for speed Former-commit-id: 727cb89041306a972f06d096ee4fce646e278f85
See https://forum.babylonjs.com/t/decals-are-not-supported-for-glb-files/34571/21
The doc has also been updated (BabylonJS/Documentation#673).
I have tried to remove a number of object creations (
Vector3/Vector4) to lower GC pressure, at least in the main paths.Also, to avoid over-complicating the code even more, I handle only the first 4 matrix indices/weights of a rigged mesh when creating new vertices at the clipping stage (vertices that are not clipped retain their full indices/weights). I did not see any artefacts because of that in my testings. This code can be revisited later if necessary.