State overlay system: Difference between revisions
Jump to navigation
Jump to search
Chris blues (talk | contribs) (→Status: add state list as a first template) |
Chris blues (talk | contribs) m (Move start parameter to status section) |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
== Objective == | == Objective == | ||
| Line 8: | Line 6: | ||
--> | --> | ||
== Status == | == Status == | ||
To start FlightGear with an existing overlay add <code>--state=statename</code> to you command line. | |||
For now there is no definitive list of possible states. These are my first suggestions: | For now there is no definitive list of possible states. These are my first suggestions: | ||
Revision as of 11:44, 14 March 2017
| This article is a stub. You can help the wiki by expanding it. |
Objective
Status
To start FlightGear with an existing overlay add --state=statename to you command line.
For now there is no definitive list of possible states. These are my first suggestions:
- parking (meaning cold and dark)
- taxi (all systems running and ready to taxi)
- take-off (standing on the runway with take-off configuration)
- cruise (cruise configuration)
- approach (approach configuration)
Background
Wayne Bragg has been working a bit with James on the state overly system.[1]
Motivation
Related
References
References
|