State overlay system: Difference between revisions
Jump to navigation
Jump to search
Chris blues (talk | contribs) m (Move start parameter to status section) |
Chris blues (talk | contribs) (add implementation) |
||
Line 15: | Line 15: | ||
* cruise (cruise configuration) | * cruise (cruise configuration) | ||
* approach (approach configuration) | * approach (approach configuration) | ||
== Implementation == | |||
To add state overlays to your aircraft, create a folder called <code>states</code>. In there you can put your <code>$state-overlay.xml</code>. | |||
Now you need to include these in your <code>$Aircraft-set.xml</code> file like this: | |||
<pre> | |||
<PropertyList> | |||
<sim> | |||
... | |||
<state include="states/parking-overlay.xml" n="0" /> | |||
<state include="states/taxi-overlay.xml" n="1" /> | |||
... | |||
</sim> | |||
</PropertyList> | |||
</pre> | |||
== Background == | == Background == |
Revision as of 11:54, 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)
Implementation
To add state overlays to your aircraft, create a folder called states
. In there you can put your $state-overlay.xml
.
Now you need to include these in your $Aircraft-set.xml
file like this:
<PropertyList> <sim> ... <state include="states/parking-overlay.xml" n="0" /> <state include="states/taxi-overlay.xml" n="1" /> ... </sim> </PropertyList>
Background
Wayne Bragg has been working a bit with James on the state overly system.[1]
Motivation
Related
References
References
|