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
I'm not a 100% sure about this, but it looks like objects with a (0,0) acceleration and a (x,0) movement (where abs(x) < 1) deactive themselves after a certain time (is_active returns false).
This means that having an object with a constant velocity of (-0.9, 0) is impossible for example.
I don't know whether this behavior is intended, but if so I think that the threshold should be configurable.
The text was updated successfully, but these errors were encountered:
tomaka
changed the title
Objects deactive themselves when they shouldn't
Objects deactivate when they shouldn't
Jul 24, 2014
I'm not a 100% sure about this, but it looks like objects with a (0,0) acceleration and a (x,0) movement (where abs(x) < 1) deactive themselves after a certain time (
is_active
returns false).This means that having an object with a constant velocity of (-0.9, 0) is impossible for example.
I don't know whether this behavior is intended, but if so I think that the threshold should be configurable.
The text was updated successfully, but these errors were encountered: