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
using Rapier 0.11.2 I'm currently trying to understand why my Rigidbodies don't fall asleep (or rather: continuously wakeup)
From reading the changelogs I found that there's something like an activation force for e.g. linvel - this doesn't seem to exist in the javascript API tho.
Is there a way to explictly set a threshold for the rigidbody when to fall asleep?
furthermore setting the translation or rotation on a collider seems to wakeup rigidbodies that are in contact with the collider (even if the collider hasn't changed it's position). When I add an extra check to only call setTranslation if the position has actually changed the Rigidbody does also sleep. Is this expected? Is there a way to prevent having to manually doing this check?
The text was updated successfully, but these errors were encountered:
I'm also looking for the ability to set a speed or time threshold for sleeping, sort of like the sleepTimeLimit and sleepTimeLimit options that the Cannon library provides. It doesn't look like Rapier has this but i could be wrong
Hello,
using Rapier 0.11.2 I'm currently trying to understand why my Rigidbodies don't fall asleep (or rather: continuously wakeup)
From reading the changelogs I found that there's something like an activation force for e.g. linvel - this doesn't seem to exist in the javascript API tho.
Is there a way to explictly set a threshold for the rigidbody when to fall asleep?
furthermore setting the translation or rotation on a collider seems to wakeup rigidbodies that are in contact with the collider (even if the collider hasn't changed it's position). When I add an extra check to only call
setTranslation
if the position has actually changed the Rigidbody does also sleep. Is this expected? Is there a way to prevent having to manually doing this check?The text was updated successfully, but these errors were encountered: