Closed khudiiash closed 2 weeks ago
Is there any hope on solving this issue this year?
Thanks for the report! the original problem seems to originate from inconsistent constant values between rapier and rapier.js.
As a workaround, you can use controller.computeColliderMovement(collider, this.vector, RAPIER.QueryFilterFlags.EXCLUDE_SOLIDS)
.
I have problems with using sensors So the setup is the following I have a player character controller, and sensors (HP bonuses) I tried everything: using QueryFilterFlags.EXCLUDE_SENSORS, using collision filters, using predicate functions, different rigidbody types, no rigidbody, different shapes - the character controller's movement is still blocked by the sensor
Moreover, world.intersectionPairsWith for character controller collider does not detect any intersections with the sensor when they must be intersecting, but they are not intersecting because the character controller simply cannot walk through the sensor. Maybe I am using it the wrong way.
version: 0.13.1 @dimforge/rapier3d
Here's the code