deactivate objects AFTER synchronizeMotionStates #2732
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the CL. I'll try to look at it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR tries to fix a bug where sometimes the final
MotionState::setWorldTransform()is not called after an active object has moved a little but was deactivated. In particular it is trying to solve a problem described in this forum thread.Dunno how safe this change is since it does subtly change the behavior of
btDiscreteDynamicsWorld::internalSingleStepSimulation(), and accidentally swaps the order ofupdateActivationState()with the internal callback, but I figured I would submit it for review. Feel free to discard, or suggest an alternative fix.