2,561
edits
m (→Major Requests) |
m (→Major Requests) |
||
Line 173: | Line 173: | ||
* http://chromium.sourceforge.net/ | * http://chromium.sourceforge.net/ | ||
* texture cropping support for 2D panels (see mailing list archives for discussions) | * texture cropping support for 2D panels (see mailing list archives for discussions) | ||
* add support for inter-texture copying to allow users to copy parts of a texture to another texture (see mailing list dicussions for details) | * add support for inter-texture copying to allow users to copy parts of a texture to another texture (see mailing list dicussions for details) | ||
* The current Property Tree code is not thread safe, sooner or later it may come in handy if this feature was added (FWIW, threaded PropertyTree implementations are provided by these two open source libraries: [http://pocoproject.org/poco/info/index.html poco] [http://www.boost.org boost]) | * The current Property Tree code is not thread safe, sooner or later it may come in handy if this feature was added (FWIW, threaded PropertyTree implementations are provided by these two open source libraries: [http://pocoproject.org/poco/info/index.html poco] [http://www.boost.org boost]) | ||
* Extend VRML/X3D or XGL support, so that proprietary formats such as *.ac can be entirely replaced using open standards http://en.wikipedia.org/wiki/COLLADA https://collada.org/public_forum/welcome.php (search the archives for COLLADA) | * Extend VRML/X3D or XGL support, so that proprietary formats such as *.ac can be entirely replaced using open standards http://en.wikipedia.org/wiki/COLLADA https://collada.org/public_forum/welcome.php (search the archives for COLLADA) | ||
* <strike>Helicopter FDM: either extend current FDM engines (i.e. yasim) to provide better support for helicopter flight dynamics, or come up with an entirely new dedicated helicopter FDM engine altogether</strike>-'''Support for helicopter flight simulation has been significantly improved meanwhile, and is still being worked on''' | * <strike>Helicopter FDM: either extend current FDM engines (i.e. yasim) to provide better support for helicopter flight dynamics, or come up with an entirely new dedicated helicopter FDM engine altogether</strike>-'''Support for helicopter flight simulation has been significantly improved meanwhile, and is still being worked on''' | ||
* add support for integration with TTS (text to speech) engines to FlightGear (i.e. Festival), so that voice ATC becomes possible. There were various discussions about this topic on the mailing list, so you may want to search the archives if you are interested in this feature. '''(Note - Festival support has already been added)''' <s>Also, there is a free multi platform TTS engine called sphinx that is siginificantly more lightweight than festival, so that it may be worth considering this to make it an optional dependency for SimGear?</s> '''Note 2: Sphinx is actually a speech recognizer, not a text-to-speech engine, AFAIK. --[[User:Josh|Josh]] 20:06, 9 May 2008 (EDT).''' | * add support for integration with TTS (text to speech) engines to FlightGear (i.e. Festival), so that voice ATC becomes possible. There were various discussions about this topic on the mailing list, so you may want to search the archives if you are interested in this feature. '''(Note - Festival support has already been added)''' <s>Also, there is a free multi platform TTS engine called sphinx that is siginificantly more lightweight than festival, so that it may be worth considering this to make it an optional dependency for SimGear?</s> '''Note 2: Sphinx is actually a speech recognizer, not a text-to-speech engine, AFAIK. --[[User:Josh|Josh]] 20:06, 9 May 2008 (EDT).''' | ||
* add moving map functionality to FlightGear (i.e. integrate atlas natively into FlightGear), so that a basic map can be directly shown within FlightGear | * add moving map functionality to FlightGear (i.e. integrate atlas natively into FlightGear), so that a basic map can be directly shown within FlightGear | ||
* the current (2D/3D) cockpit panel code is not yet particularly efficient, would be good if someone could optimize it some more | * the current (2D/3D) cockpit panel code is not yet particularly efficient, would be good if someone could optimize it some more | ||
* add support for tutorials/lessons (think, flight school) to FlightGear (see earlier mailing list discussions for details) '''(Note - tutorials have already been added; check the Help menu in the default C172 or Lightning)''' | * add support for tutorials/lessons (think, flight school) to FlightGear (see earlier mailing list discussions for details) '''(Note - tutorials have already been added; check the Help menu in the default C172 or Lightning)''' | ||
=== Huge Requests === | === Huge Requests === |
edits