20,741
edits
FGAIS: Difference between revisions
Jump to navigation
Jump to search
→Issues
(→Issues) |
|||
| Line 43: | Line 43: | ||
=== Issues === | === Issues === | ||
* Altitude need to be computed with the climb rate calculated with the updateAIAircraf(); | |||
* When aircraft is on ground, planefinder.net send altitude=0 even if the runway is on top Everest mountain... It seem that planefinder send us a relative altitude when aircraft is on ground and send us absolute altitude when aircraft is flying. | |||
At the moment, the fgais background thread will sleep until 60 seconds have passed, only then, will it start downloading/parsing/computing new data. However, by that time, the fgms main thread is already "starving", because it has no more data to send to the fgfs client - in other words, it has to wait until the worker thread has completed. We should be preparing a new set of data earlier than that. For now, a usable workaround would be to compute even more data and use a FIFO | At the moment, the fgais background thread will sleep until 60 seconds have passed, only then, will it start downloading/parsing/computing new data. However, by that time, the fgms main thread is already "starving", because it has no more data to send to the fgfs client - in other words, it has to wait until the worker thread has completed. We should be preparing a new set of data earlier than that. For now, a usable workaround would be to compute even more data and use a FIFO | ||
| Line 79: | Line 83: | ||
Currently our extrapolation routine doesn't apply climb rate, we need to implement this. | Currently our extrapolation routine doesn't apply climb rate, we need to implement this. | ||
=== Roadmap === | === Roadmap === | ||