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

Fix incorrect linear velocity of the vehicle chassis #4679

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

DVLP
Copy link
Contributor

@DVLP DVLP commented Dec 6, 2024

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.

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

Successfully merging this pull request may close these issues.

1 participant