Plan-zakalawe: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
Line 15: Line 15:
* Extend the GPS code to support more flight-plan functions and en-route information
* Extend the GPS code to support more flight-plan functions and en-route information
** Climb/descent computations, based on some aircraft performance data
** Climb/descent computations, based on some aircraft performance data
* Add proper support for special leg types, ideally equivalent to [[ARINC-424]] path-terminators. This implies support for [[DME arc]], heading to fix, heading until crossing radial, holding pattern and assorted other special leg behaviours.
* Create a new generic 3D instrument for the KLN89b, using Nasal and the updated GPS code
* Create a generic 3D instrument modelling a Delco Carousel INS, using the GPS as the backend
* Investigate creating a special camera/view mode and input context so a GPS, FMS or other 3D instrument can occupy most of the screen, and intercept key presses. GUI dialogs must solve the keyboard input issue already. Imagining that a click on the instrument animates the camera to a 'face on' view, and click outside the instrument returns to the previous view point.
* Add GPS precision approach support
** Define an on-disk format for defining approaches. This will likely be similar to the navdata.org / PIC-767 XML format
** Add approach and missed-approach modes to the GPS code
* Extend the route manager to allow basic flight-planning
** Generate a route using a search: VOR-VOR, airways or GPS direct.
** Thomas Forster has generic routing code for this
* Allow performance data to be specific per-aircraft
* Allow performance data to be specific per-aircraft
** Initially, basic information such as cruise speed, best climb rates, and so on
** Initially, basic information such as cruise speed, best climb rates, and so on

Revision as of 17:52, 31 December 2011

Task List

Short term plans

Areas

General areas I'm working on, or planning to work on

FGPositioned

  • Re-investigate caching data in a binary format to accelerate startup time (avoid reading nav.dat, apt.dat on launch, and scenery airport data repeatedley)

GPS / FMS / Route-planning

  • Extend the GPS code to support more flight-plan functions and en-route information
    • Climb/descent computations, based on some aircraft performance data
  • Allow performance data to be specific per-aircraft
    • Initially, basic information such as cruise speed, best climb rates, and so on
    • Weight/balance tables
    • Vspeeds computations

NAV Display

  • Improve API based on feedback from aircraft authors!

Miscellaneous