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 13:10, 10 November 2007
, 10 November 2007→Intermediate Requests
m (striking out the lack of helicopter support) |
|||
| Line 136: | Line 136: | ||
* add support for vector images (SVG) to FlightGear, so that FlightGear can use vector images natively (should also reduce the base package size) [[SVG_RESOURCES]] | * add support for vector images (SVG) to FlightGear, so that FlightGear can use vector images natively (should also reduce the base package size) [[SVG_RESOURCES]] | ||
* add support to enable users to disable 3D cockpit rendering for multiplayer/AI aircraft | * add support to enable users to disable 3D cockpit rendering for multiplayer/AI aircraft | ||
* extend nasal interpreter to provide functions for loading and saving XML files directly, preferably also wrapping the functions from props_io.cxx for nasal | * <strike>extend nasal interpreter to provide functions for loading and saving XML files directly</strike> '''DONE''', preferably also wrapping the functions from props_io.cxx for nasal | ||
* provide support for optional use of VoIP (voice over IP) clients within FlightGear, so that such clients can be used for ATC-specific purposes (there were various discussions with plenty of good ideas mentioned on the mailing list) | * provide support for optional use of VoIP (voice over IP) clients within FlightGear, so that such clients can be used for ATC-specific purposes (there were various discussions with plenty of good ideas mentioned on the mailing list) | ||
* merge AI and ATC code so that both work properly with each other | * merge AI and ATC code so that both work properly with each other | ||
* add support for a TCAS implementation that honors multiplayer as well as AI traffic | * add support for a TCAS implementation that honors multiplayer as well as AI traffic | ||
* 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 ) | ||
* expose the nasal interpreter via network/telnet, so that scripts can be remotely inserted and executed. | * <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) | * implement a flight director (using the current PID controller code) | ||
* provide support for force-feedback input hardware and/or motion platforms | * provide support for force-feedback input hardware and/or motion platforms | ||