Tracking: Game-readiness of @react-three/rapier

[hmans]

I'm using this ticket as a high-level overview of things that are still missing for the library to be "game-ready". Please ready this merely as a tracking issue, not a wishlist. :-) I will be implementing some of these myself, and submitting them via PR. Also please consider this a living document, I will probably add a thing or two to this list over time.

Must Have:

• Make update priority configurable. (Introduce updatePriority prop to <Physics> #78)
• Clamp deltatime values to 1s max. (fix: clamp deltatime values to 1 second. #85)
• Either provide interpolation for translation (currently disabled), or allow the user to configure a varying time step. (Currently, using a lerping follow camera immediately makes the non-interpolated "jumpy" nature of rigidbody movements very obvious.)
• Allow the user to use sensors. (feat(colliders): added the ability to use sensors on colliders #90?)
• Allow setting of restrictRotations and restrictTranslations on rigidbodies. (see rapier docs) This is now enabledRotations and enabledTranslations, and it's already in, yay!

Should Have:

• Allow for per-collider collision callbacks. (WIP: Collisions Upgrade! #83)
• Easy convex collider generation from any geometry, including loaded GLTFs.
• Allow the user to specify the density of colliders (or a default value on RigidBody.) (Rapier is nice in that it will automatically calculate the mass from the density and the volume of the colliders.)
• Allow the user to access a rigidbody's scene object through the ref/API. (RigidBodies wrap their children in an <object3D> scene object, but don't expose them through their API. Systems that need to interact with the scene object currently only have the option of establishing their own wrapper object and storing the ref to that separately.)
• The RigidBodyApi should not force bodies that it interacts with to wake up. This decision should be left to the user (but it would be fine to default this to true.) (fix: allow control of wakeUp #125)
• The scene object created by RigidBodies and Colliders should default to matrixAutoUpdate={false}, and have their matrices updated explicitly (or this attribute toggled) when the owning rigidbody is awake (ie. not sleeping).
  • Sleeping bodies will never move, so disabling their automatic matrix recalculations is a good optimizations for scenes with larger amounts of rigid bodies (a large portion of which might be sleeping.)
  • It'd be okay to make this optimization opt-in

Nice to Have:

• Easy to use physics debugger
• Support for Rapier 2D #113

[firtoz]

Made #101 before seeing this, I guess that will satisfy one of the checkboxes here? :D