-
Notifications
You must be signed in to change notification settings - Fork 89
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
Tickrate sensors too low #166
Comments
disclaimer: all these tests are run on my local computer. PawnSimApi.updateKinematics is being called at 140 hz with no ros bridge connected. With ros bridge connected it is a lot more unstable, jumping between 40 and 140 hz. Primary suspect at this moment: cameras |
Yes, when no camera's configured the tickrate stays nicely at 140hz. freaking cameras #43 |
No cameras: 149 noise is not the problem |
Tickreate is not as steady as it seemd. In 300 ticks (without cameras) the smallest delay between ticks was 1/259 second and the largest delay was 1/90 second. That is a pretty big delay. |
As you can see in these pr's, ive been trying to get this to work. At this moment the carstate is updated 100hz , but somehow the odometry still only provides new data 37 hz. I have to leave this be for now because other thing are more important. :/ |
At this moment the physics engine updates the state of the car 40 times a second (when fully equipped with cameras and Lidars). This is too low because groundspeedsensor, odometery, imu and car controlls need to operate at much higher rate. Let's try to get the tickrate of the game up to at least 100hz.
The text was updated successfully, but these errors were encountered: