-
Notifications
You must be signed in to change notification settings - Fork 80
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
Improve camera performance #43
Comments
We found that splitting the camera sensor code from the ros_bridge into it's own node greatly improves the performance. After #95 the performance is 30 fps (2x 785x785, local computer, NoDisplay, flying map` without lidar. We are not there yet but getting closer. |
Tested camera's in a competition setup: 2 google cloud instances as described in the integration guide. One dedicated to running the simulation, the other one receiving the sensordata and sending setpoints. Using this settings.json. We got around 20 fps on both camera's |
Sorry, but this turned out to be too complicated to be finished before FSOnline competition. |
At this moment the cameras are laggy. With 3 camera framerate can drop to 3 fps and with 1 camera it drops to 20 fps. We want: steady 30 fps for the onboard camera and the livestream angle.
This is the epic adventure to make the simulator performant.
The text was updated successfully, but these errors were encountered: