8,827
edits
Feature Requests / Proposals / Ideas: Difference between revisions
Jump to navigation
Jump to search
m
Feature Requests / Proposals / Ideas (view source)
Revision as of 17:01, 20 September 2008
, 20 September 2008no edit summary
m (adding note WRT "resumable replay subsystem" RFE) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{cleanup}} | |||
'''Please note:''' We now have a a tracker on | '''Please note:''' We now have a a tracker on [http://sourceforge.net/tracker/?group_id=583 SourceForge]. Please list your bug/feature request/enhancement/idea on SourceForge as well as here. | ||
Occasionally, people join the [[FlightGear]] mailing lists offering to contribute to FlightGear and asking where they might start contributing, apparently often hoping for some sort of official "TODO" list or at least some sort of semi-official roadmap. Unfortunately, nothing like this exists so far for FlightGear and the closest thing to a "TODO" page, the "Goals page", has apparently not really been updated for several years. | |||
Occasionally, people join the FlightGear mailing lists offering to contribute to FlightGear and asking where they might start contributing, apparently often hoping for some sort of official "TODO" list or at least some sort of semi-official roadmap. Unfortunately, nothing like this exists so far for FlightGear and the closest thing to a "TODO" page, the "Goals page", has apparently not really been updated for several years. | |||
So it is understandably hard for new community members to get a good grasp of the current development status and -progress, as well as to identify areas where FlightGear might use some improvement if they have not followed the recent mailing list discussions. | So it is understandably hard for new community members to get a good grasp of the current development status and -progress, as well as to identify areas where FlightGear might use some improvement if they have not followed the recent mailing list discussions. | ||
| Line 24: | Line 23: | ||
* [http://pigeond.net/flightgear/fglive.html FG Live CD] | * [http://pigeond.net/flightgear/fglive.html FG Live CD] | ||
* [http://squonk.abacab.org/dokuwiki/fgcom FGCOM - FlightGear Radio Comms] | * [http://squonk.abacab.org/dokuwiki/fgcom FGCOM - FlightGear Radio Comms] | ||
'''IMPORTANT:''' before you actually start working on any of these efforts, it is important to subscribe to the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear Developer's mailing list] to discuss your plans (alternatively you may also want to check out the FlightGear IRC channel: irc.flightgear.org #flightgear | '''IMPORTANT:''' before you actually start working on any of these efforts, it is important to subscribe to the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear Developer's mailing list] to discuss your plans (alternatively you may also want to check out the FlightGear IRC channel: irc.flightgear.org #flightgear | ||
| Line 31: | Line 28: | ||
So please make sure to talk about your plans with other contributors and especially '''with the maintainer !!''' of the respective project before starting your work, because ideas listed on this page don't necessarily match the intended/planned direction of development. | So please make sure to talk about your plans with other contributors and especially '''with the maintainer !!''' of the respective project before starting your work, because ideas listed on this page don't necessarily match the intended/planned direction of development. | ||
== User Perceived Improvements == | == User Perceived Improvements == | ||
| Line 52: | Line 43: | ||
Evaluating the merits of such discussions should eventually enable us to determine which areas in FlightGear need to be specifically addressed in order to make FlightGear appeal to more users. Please feel free to add new entries. | Evaluating the merits of such discussions should eventually enable us to determine which areas in FlightGear need to be specifically addressed in order to make FlightGear appeal to more users. Please feel free to add new entries. | ||
=== General === | === General === | ||
| Line 126: | Line 116: | ||
== Feature Requests == | == Feature Requests == | ||
=== Minor Requests === | === Minor Requests === | ||
* Create or modify existing DTDs/Schemas for the various PropertyList encoded XML file formats that FlightGear currently supports (FDM, Aircraft, GUI, Sounds etc.), so that such DTDs or Schemas can be used by XML editors and validators. | * Create or modify existing DTDs/Schemas for the various PropertyList encoded XML file formats that FlightGear currently supports (FDM, Aircraft, GUI, Sounds etc.), so that such DTDs or Schemas can be used by XML editors and validators. | ||
* <del>Add support for an optional framerate limiting mode (configurable, default i.e. 60-70fps), this can safe CPU cycles on many platforms (no useless idling/sleep() )</del> available: /sim/frame-rate-throttle-hz | * <del>Add support for an optional framerate limiting mode (configurable, default i.e. 60-70fps), this can safe CPU cycles on many platforms (no useless idling/sleep() )</del> available: /sim/frame-rate-throttle-hz | ||
| Line 147: | Line 136: | ||
* implement a "failure/crash" (limits?) subsystem that can be XML-configured with tailored values and limits for specific aircraft (i.e. max allowable speeds in various configurations, max allowable pitch up/down, roll angle, g load etc.). That way, it would be up to aircraft authors to provide such limits for their aircraft in some sort of easily modifiable XML file and FlightGear could optionally honor these values at runtime (currently, it is no problem to extend the gear or flaps at ridiculously high speeds, or crash-land an airliner and keep flying afterwards-this would certainly add a good portion of realism to FlightGear and could still be kept entirely optional). | * implement a "failure/crash" (limits?) subsystem that can be XML-configured with tailored values and limits for specific aircraft (i.e. max allowable speeds in various configurations, max allowable pitch up/down, roll angle, g load etc.). That way, it would be up to aircraft authors to provide such limits for their aircraft in some sort of easily modifiable XML file and FlightGear could optionally honor these values at runtime (currently, it is no problem to extend the gear or flaps at ridiculously high speeds, or crash-land an airliner and keep flying afterwards-this would certainly add a good portion of realism to FlightGear and could still be kept entirely optional). | ||
* provide a GUI dialog that automatically enumerates all available instrumentation systems, so that users can easily enable/disable individual systems | * provide a GUI dialog that automatically enumerates all available instrumentation systems, so that users can easily enable/disable individual systems | ||
* add a native flight planning facility to FlightGear, so that VFR/IFR flights can be planned (loaded and saved) and optionally be passed on (filed) to the AI/ATC subsystems, this will probably require the base package to be extended with terminal approach/departure data. | * add a native flight planning facility to FlightGear, so that VFR/IFR flights can be planned (loaded and saved) and optionally be passed on (filed) to the [[AI]]/[[ATC]] subsystems, this will probably require the base package to be extended with terminal approach/departure data. | ||
* provide runtime configurable friction coefficients for runways to simulate contaminated runways (dirt, water, snow/ice) at runtime and export corresponding properties to property tree | * provide runtime configurable friction coefficients for runways to simulate contaminated runways (dirt, water, snow/ice) at runtime and export corresponding properties to property tree | ||
* extend weather modelling subsystem to simulate weather features such as thermals, gusts or windshear more extensively and realistically. This would also come in very handy for sailplane/gilder modelling which is currently not yet satisfactorily simulated. | * extend weather modelling subsystem to simulate weather features such as thermals, gusts or windshear more extensively and realistically. This would also come in very handy for sailplane/gilder modelling which is currently not yet satisfactorily simulated. | ||
| Line 249: | Line 238: | ||
* add support for automatically created scenery objects to populate the scenery dynamically at runtime (autogen-like), this could add quite a portion of realism to FlightGear without having to model scenery manually using fgsd, yet one could still use fgsd for areas where people are willing to contribute. All other scenery should by default be populated using autogen buildings and objects (references: http://www.infinitylab.com.au/research/prototypes.htm and http://vterrain.org/Culture/BldCity/procedural.html and http://pcity.sourceforge.net/ ) | * add support for automatically created scenery objects to populate the scenery dynamically at runtime (autogen-like), this could add quite a portion of realism to FlightGear without having to model scenery manually using fgsd, yet one could still use fgsd for areas where people are willing to contribute. All other scenery should by default be populated using autogen buildings and objects (references: http://www.infinitylab.com.au/research/prototypes.htm and http://vterrain.org/Culture/BldCity/procedural.html and http://pcity.sourceforge.net/ ) | ||
== | == Related content == | ||
* [[Bugs]] | |||
* [[Project Infrastructure Enhancements]] | |||