Feature Requests / Proposals / Ideas: Difference between revisions

Jump to navigation Jump to search
m
adding pointers to "wishlist" threads on forum
(adding pointer to related RFE (runtime configurable friction coefficients for ground interaction))
m (adding pointers to "wishlist" threads on forum)
Line 26: Line 26:
'''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 (additionally 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 (additionally you may also want to check out the FlightGear IRC channel: irc.flightgear.org #flightgear
), this is extremely important in order to avoid duplicate code/efforts and a lack of coordination with regard to relevant implementation details.
), this is extremely important in order to avoid duplicate code/efforts and a lack of coordination with regard to relevant implementation details.
In addition, it's worth pointing out that this wiki page may not necessarily be "up2date" with the latest developments in FlightGear.


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 FlightGear component or affiliated 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 43: Line 44:


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.
The FlightGear forums are another place where users frequently come up with "wishlists" of features that they'd like to see in FlightGear:
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=3090 "Wishlist for FlightGear" Thread on FlightGear forums - 03/2009]
* [http://www.flightgear.org/forums/viewtopic.php?f=6&t=3085 "Unlimited Wishlist" Thread on FlightGear forums - 02/2009]
(None of these threads have so far been evaluated or incorporated here)


=== General ===
=== General ===
Line 117: Line 126:
== Feature Requests ==
== Feature Requests ==
=== Minor Requests ===
=== Minor Requests ===
* The fgfs multiplayer system currently seems to resend positional properties even during replay mode [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg19471.html], so that the full replay is transmitted to the multiplayer server where it may cause unnecessary confusion - this should be fairly easy to fix by making the current behaviour optional via a corresponding runtime-configurable property.
* 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
2,561

edits

Navigation menu