Common aircraft properties: Difference between revisions
Fusionstream (talk | contribs) (Draft) |
Fusionstream (talk | contribs) (→WORK IN PROGRESS: Added a bit of text to counter Gij's claim of existing defaults.) |
||
| Line 4: | Line 4: | ||
TODO: standardise locations most common to existing aircraft to ease transition | TODO: standardise locations most common to existing aircraft to ease transition | ||
With common aircraft properties found in uncommon locations, assigning buttons in joysticks to certain functions became mostly a hit or miss affair. | With common aircraft properties found in uncommon locations, assigning buttons in joysticks to certain functions became mostly a hit or miss affair. e.g. Speedbrakes and thrust reversers are found in different location in the property tree, even across official FlightGear planes! Without standard locations, joystick code tends to be aircraft specific. | ||
There was an [http://code.google.com/p/flightgear-bugs/issues/detail?id=1173 attempt to unify it all with a nasal script] but after consulation and comments with others, this attempt was replaced with the solution to standardise common aircraft properties in standardised locations. | There was an [http://code.google.com/p/flightgear-bugs/issues/detail?id=1173 attempt to unify it all with a nasal script] but after consulation and comments with others, this attempt was replaced with the solution to standardise common aircraft properties in standardised locations. | ||
Revision as of 03:28, 31 July 2013
 |
Work in progress This article or section will be worked on in the upcoming hours or days. See history for the latest developments. |
WORK IN PROGRESS
TODO: standardise locations most common to existing aircraft to ease transition
With common aircraft properties found in uncommon locations, assigning buttons in joysticks to certain functions became mostly a hit or miss affair. e.g. Speedbrakes and thrust reversers are found in different location in the property tree, even across official FlightGear planes! Without standard locations, joystick code tends to be aircraft specific.
There was an attempt to unify it all with a nasal script but after consulation and comments with others, this attempt was replaced with the solution to standardise common aircraft properties in standardised locations.
This document will exhaustively list property tree locations where aircraft developers should store their common aircraft properties (if not alias them).
Gear
Properties marked with an '✲' are standard across all aircraft and should always be set. For example, an old aircraft without any autobrakes should still define /controls/gear/autobrake although set it to 0
States
- In /controls/gear
- /controls/gear/brake-parking ✲
0 = Off
1 = On - /controls/gear/brake-chokes ✲
0 = Off
1 = On - /controls/gear/antiskid ✲
0 = Off
1 = On - /controls/gear/autobrake ✲
0 = Fully Off
1 = Fully On - /controls/gear/launcbar ✲
- /controls/gear/servicable ✲
- /controls/gear/brake-servicable
- /controls/gear/brake-temperature
- /controls/gear/brake-hydraulic-pressure
- /controls/gear/tyre-temperature
- /controls/gear/tyre-pressure
- /controls/gear/brake-available ✲
- /controls/gear/retractable ✲
- /controls/gear/brake ✲
- /controls/gear/gear-down
0 = Retracted
1 = Extended
- /controls/gear/brake-parking ✲
- In /controls/gear/gear[n]
Transitions
- In /gear/gear[n]
- /gear/gear[n]/position-norm
0 = Fully Retracted
0.x = Transitioning
1 = Fully Extended
- /gear/gear[n]/position-norm
- In /controls/gear/gear[n]
brake-pressure 0 0.x 1 friction-ground friction-ground-real friction-bearing friction-bearing-real friction-side-slip friction-side-slip-real
Speedbrakes
engine --thrust reversers
flaps
tailhook
radios - /instrumentation/nav
fuel
implementation with custom locations: if you require your values be stored in a custom location, be sure to alias them in the standard location: <property alias="../../params/n1"/>h