Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Objects deactivate when they shouldn't #11

Closed
tomaka opened this issue Jul 24, 2014 · 1 comment
Closed

Objects deactivate when they shouldn't #11

tomaka opened this issue Jul 24, 2014 · 1 comment

Comments

@tomaka
Copy link

tomaka commented 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.

@tomaka tomaka changed the title Objects deactive themselves when they shouldn't Objects deactivate when they shouldn't Jul 24, 2014
@sebcrozet
Copy link
Member

You are right, any object with a total velocity magnitude bellow a hard-coded threshold of 1.0 will be frozen after some times.

I will make this threshold customizable on a per-rigid-body basis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants