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

Incorrect velocity transference after new Element/Construction/... creation #7

Open
NotSoOld opened this issue Jul 3, 2019 · 0 comments
Assignees
Labels

Comments

@NotSoOld
Copy link
Owner

NotSoOld commented Jul 3, 2019

It's about managing collision events at high speeds (and destruction because the speed was too high).
It seems to be too late to perform the transference like new.velocity = old.velocity. Old.velocity at this time is already very low as the collision already happened. Should store the velocity value for future application.
The same goes about applying the velocity to detached Fragments. The object which pushed them stopped already, so they receive 0 velocity change after gaining a Rigidbody. Hint: when colliding, the Collision parameter has an impulse property (and, probably, more useful properties), could use it.

@NotSoOld NotSoOld added the bug label Jul 3, 2019
@NotSoOld NotSoOld self-assigned this Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant