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

Testbed is slow to respond #13

Open
Nickelium opened this issue Apr 25, 2017 · 3 comments
Open

Testbed is slow to respond #13

Nickelium opened this issue Apr 25, 2017 · 3 comments

Comments

@Nickelium
Copy link

When running the autopilot on the provided testbed we get about 5 to 6 fps.
While with our own testbed the framerates varies from 17 to 22 fps.

Tested on an Intel i7-4710HQ 2.5Ghz and Nvidia Geforce 850M 2Gb.

@samldd
Copy link
Member

samldd commented Apr 25, 2017

My version of the testbed waits until the timeHasPassed() method of the drone has finished, does yours also wait, or does it just notify the drone? If this seems to be the problem I will have another look at the implementation to make it go on while your drone is making calculations

@Nickelium
Copy link
Author

Our version of the testbed also waits before resuming.

@timower
Copy link

timower commented May 18, 2017

We have the same problem, when the timestep is too low the simulation is very slow.
But when we increase the timestep too much the drone becomes unstable because
too much time passes between frames.

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

No branches or pull requests

3 participants