FG1000
| This article is a stub. You can help the wiki by expanding it. |
Motivation
|
|
The enormous variety in current glass flight decks means we really need to think of a new way of defining glass cockpit layouts.[1]
The airspace system is in the process of changing drastically [...] this isn't just a matter of throwing up a canvas showing some GPS waypoints and a magenta line. Modern navigators are astoundingly-complex devices — probably an order of magnitude more lines of code than FlightGear itself — and even their basic flight planning algorithms and databases (e.g. fly-by waypoints vs fly-over waypoints, open vs closed approach procedures, transitions into RNAV approaches, etc.) are far beyond the scope of anything we've tried, and we'd also need an up-to-date database far more complex than the ones we have now. Once you get to the extra features, like FIS-B weather or TIS-B traffic info over ADS-B, or TAWS (terrain alerting), we're probably in way over our heads trying to emulate even the simplest general-aviation IFR GPS.
Depending on how we deal with this challenge, the question is whether that means that the usefulness of FlightGear will also gradually taper off. [2]
Background
|
|
Status
|
|
Related
References
|