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
There is an update in the GLTF structure, now they can accept physics, babylonJs already have implemented it, but there's no example with Three.js. So this could be hard to do.
As we need to investigate if this is possible directly here in this pkg, if we need to make changes in the GLTF parser provided by Three.js (or if we can extend it) and the match them with the components provided by Rapier itself.
Please read the link below for more information.
Suggested solution
Much of the result will define the output. But reading about it, a new component could be a good solution. import { PhysicalGLTF } from ...` (of course the name has to be defined).
Other option could be adding extension to the existing useGLTF composable provided by cientos
I would prefer not to modify cientos directly for this one. WDYT?
Description
There is an update in the GLTF structure, now they can accept physics, babylonJs already have implemented it, but there's no example with Three.js. So this could be hard to do.
As we need to investigate if this is possible directly here in this pkg, if we need to make changes in the GLTF parser provided by Three.js (or if we can extend it) and the match them with the components provided by Rapier itself.
Please read the link below for more information.
Suggested solution
Much of the result will define the output. But reading about it, a new component could be a good solution.
import { PhysicalGLTF } from
...` (of course the name has to be defined).Other option could be adding extension to the existing
useGLTF
composable provided bycientos
I would prefer not to modify cientos directly for this one. WDYT?
Alternative
Any other alternative is welcome
Additional context
Please check:
Validations
The text was updated successfully, but these errors were encountered: