You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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.
The text was updated successfully, but these errors were encountered: