Feature Requests / Proposals / Ideas: Difference between revisions

Jump to navigation Jump to search

Feature Requests / Proposals / Ideas (view source)

Revision as of 09:39, 29 October 2009

3,912 bytes removed ,  29 October 2009
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)
* <strike>add support for enhanced water modeling, so that we can start implementing water aircraft with floats etc.</strike>-'''in progress as of 11/2007'''
* 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])
* Meanwhile, FlightGear has become a pretty monolothic piece of software, in the long run it would be desirable if the code could become somewhat more modularized and structured, eventually this should also make it easier for new contributors to get started.
* <del>add support for decoding ESRI shapefiles, so that we can later on render them to a texture to be displayed on certain instruments, Dave Luff recently mentioned that he would need similar functionality for his KLN89, too. This would probably also be useful for scenery creation in general and in order to modify scenery appearance [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15699.html according to region specific information] http://freshmeat.net/projects/shapelib/ http://sourceforge.net/projects/shpread/</del>
** NOTE: The Scenery generation process is already several steps ahead of this proposal and uses a PostgreSQL/PostGIS database which, as an additional feature, offers Shapefiles to be exported on-the-fly. Visit: [http://mapserver.flightgear.org/download.psp Landcover-DB Shapefile download]
* 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
* add support for adding, placing and modifying scenery objects within the scenery dynamically at runtime-possibly using the property tree to enumerate all active scenery objects, so that attributes can be changed at runtime
* 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)'''
* More and more often, users of other flight simulators with lacking scenery support (such as Aerowinx Precision Sim)  would like to use FlightGear in conjunction with their commercial simulator in order to create a FlightGear-based visual scenery representation. To some extent this works already quite well due to the possibility to provide an external/null FDM. However it is not uncommon to see more or less significant differences in the underlying databases (navaids, terrain, airports/runways),so that for example, navaids in other simulators do not match the positions in FlightGear and vice versa. Likewise, for airports and runways. Currently, the only workaround is to manually hardcode corresponding offsets in order to compensate for this. However, in the long run it would be nice if there was a standardized mechanism in FlightGear to automatically align databases for navaids, airports, runways, terran and possibly also important scenery objects (landmarks). This could probably be based on a mechanism to allow other simulators to request/send positional information for a navaid, airport/runway so that FlightGear could automatically compensate for differences by auto-aligning the corresponding coordinates at runtime. Preferably, something like this would be exposed via a network interface (i.e. telnet) so that it would become very straight forward to interface with FlightGear. In the long run, such a facility would also make it possible to use different sets of underlying data in FlightGear easily. [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16047.html]
* Allow arbitrary custom views to be rendered to a texture, so that the created texture can be used to create instruments that feature some sort of "outside view", i.e. an advanced HUD or the external view of an A340 (camera mounted on the tail), this would enable us to show external views on an instrument in the cockpit panel. We only need something that allows us to define a custom instrument layer type that gets its contents from a specific user defined (or global) view.
* Extend the RenderTexture class to provide support for Frame Buffer Object based rendering to a texture, this is a relatively new way to support rendering to texture for platforms or OpenGL (driver) implementations that do not offer native RTT support, as it is the case for many older Linux cards: http://openvidia.sourceforge.net/fbo.shtml


=== Huge Requests ===
=== Huge Requests ===
MILSTD
2,561

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/16965"

Navigation menu