20,741
edits
Startup Profiles: Difference between revisions
Jump to navigation
Jump to search
→Status
(→Status) |
|||
| Line 42: | Line 42: | ||
<references/> | <references/> | ||
== | == Original Idea == | ||
{{ | Here are a few usability guidelines that might help: | ||
| | # Consistency - all aircraft should start in same default state as far as possible (obviously, a glider doesn't have an engine), so that a user isn't surprised when switching aircraft types. | ||
# Configurability - it should be not only possible but very easy for a user to override the default state without editing XML or Nasal files. | |||
# Simplicity - the default state should be the easiest one for new users. Experienced users will have an easier time changing the default. | |||
<ref> {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/15602927/ | |||
| title = <nowiki>[Flightgear-devel] Consistent aircraft states</nowiki> | |||
| author = <nowiki>David Megginson</nowiki> | |||
| date = Oct 12th, 2007 | |||
| added = Oct 12th, 2007 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
We introduce a new global property, such as /sim/start-state, which can be set to (say) "parked", "in-air", or "idling". The configuration files for every aircraft could respect that property, so that if you set it to "parked", *every* aircraft (even the default 172) would start parked, etc. (we could even put it on the apron instead of the runway if we add parking coordinates to the airports file). I think "idling" should be the default the first time someone runs FlightGear, since it's standard with all flight sims and by far the easiest for new users, but one menu selection should be able to switch to "parked" for people (like you) who prefer to go through the startup and taxiing routine every time.<ref> {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/15602927/ | | url = http://sourceforge.net/p/flightgear/mailman/message/15602927/ | ||
| title = <nowiki>[Flightgear-devel] Consistent aircraft states</nowiki> | | title = <nowiki>[Flightgear-devel] Consistent aircraft states</nowiki> | ||
| Line 53: | Line 65: | ||
| script_version = 0.25 | | script_version = 0.25 | ||
}} | }} | ||
}} | </ref> | ||
instead of having each designer decide, let the users start the aircraft any way *they* want. I think the default should be with the engine on and idling, but that's a separate discussion. The first step is to agree on a global property and start modifying aircraft configs to honour it; then we can debate what the default value of that property should be. | |||
<ref>{{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/15602936/ | |||
| title = <nowiki>Re: [Flightgear-devel] Consistent aircraft states</nowiki> | |||
| author = <nowiki>David Megginson</nowiki> | |||
| date = Oct 12th, 2007 | |||
| added = Oct 12th, 2007 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
== Status == | |||
{{Note|as of 04/2016, a new proposal is being discussed on the FlightGear devel list}} | {{Note|as of 04/2016, a new proposal is being discussed on the FlightGear devel list}} | ||