2,561
edits
Feature Requests / Proposals / Ideas: Difference between revisions
Jump to navigation
Jump to search
m
Feature Requests / Proposals / Ideas (view source)
Revision as of 02:33, 1 November 2008
, 1 November 2008updating progress: flight directors are modeled in various aircraft →Intermediate Requests
m (limits are supported already) |
m (updating progress: flight directors are modeled in various aircraft →Intermediate Requests) |
||
| Line 152: | Line 152: | ||
* add support for flight path visualization within FlightGear, possibly so that it can optionally be enabled for external or replay views ( http://www.flightgear.org/Projects/SynthVision/ http://www.cobbin.com/synthetic-vision.htm ) | * add support for flight path visualization within FlightGear, possibly so that it can optionally be enabled for external or replay views ( http://www.flightgear.org/Projects/SynthVision/ http://www.cobbin.com/synthetic-vision.htm ) | ||
* <strike>expose the nasal interpreter via network/telnet, so that scripts can be remotely inserted and executed.</strike> this can be basically done already by writing new code to properties and executing the code in the property | * <strike>expose the nasal interpreter via network/telnet, so that scripts can be remotely inserted and executed.</strike> this can be basically done already by writing new code to properties and executing the code in the property | ||
* implement a flight director (using the current PID controller code) | * <del>implement a flight director (using the current PID controller code)</del> FDs are meanwhile available in several aircraft | ||
* provide support for force-feedback input hardware and/or motion platforms | * provide support for force-feedback input hardware and/or motion platforms | ||
* for the development of more advanced avionics we will require a terminal procedures database (i.e. SIDs & STARs), this should be added to the base package, so that we can provide the corresponding data within FlightGear, its availability (memory consumption!) could be made optional using a corresponding property or new special instrument type. | * for the development of more advanced avionics we will require a terminal procedures database (i.e. SIDs & STARs), this should be added to the base package, so that we can provide the corresponding data within FlightGear, its availability (memory consumption!) could be made optional using a corresponding property or new special instrument type. | ||