Fix incorrect linear velocity of the vehicle chassis#4679
Open
DVLP wants to merge 1 commit intobulletphysics:masterfrom
Open
Fix incorrect linear velocity of the vehicle chassis#4679DVLP wants to merge 1 commit intobulletphysics:masterfrom
DVLP wants to merge 1 commit intobulletphysics:masterfrom
Conversation
When the vehicle is completely stationary its linear velocity obtained with getLinearVelocity in Y axis is always positive and quite high i.e. 0.15. That's not any oscillation but a steady value of a stationary value. I noticed that getCurrentSpeedKmHour is not equal to getLinearVelocity.length() * 3.6 when the simulation step is finished, it only is equal when m_currentVehicleSpeedKmHour is stored. After some investigation I found that impulses added to the vehicle body by the suspension are not being processed until the next simulation step. This change allows the linear velocity to be reported correctly. It may also reduce input lag by one step. I'm only not sure if updateActions shouldn't be even higher. Being above integrateTransforms is enough to fix the linear velocity issue.
Contributor
Author
|
Actually this PR fixes one thing but breaks another. It makes the wheels lag behind the car by 1 frame. To make this work |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When the vehicle is completely stationary its linear velocity obtained with getLinearVelocity in Y axis is always positive and quite high i.e. 0.15. That's not any oscillation but a steady value of a stationary body. I noticed that getCurrentSpeedKmHour is not equal to getLinearVelocity.length() * 3.6 when the simulation step is finished, it only is equal when m_currentVehicleSpeedKmHour is being stored. After some investigation I found that impulses added to the vehicle body by the suspension are not being processed until the next simulation step. This change allows the linear velocity to be reported correctly. It may also reduce input lag by one step. I'm only not sure if updateActions shouldn't be even higher. Being above integrateTransforms is enough to fix the linear velocity issue.