20,741
edits
Startup Profiles: Difference between revisions
Jump to navigation
Jump to search
→Motivation
| Line 5: | Line 5: | ||
== Motivation == | == Motivation == | ||
The position init code is pretty ugly as people have added many different (useful!) options over the years | |||
<ref>{{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/31631648/ | |||
| title = <nowiki>Re: [Flightgear-devel] Aircraft positioning on the runway</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Nov 12th, 2013 | |||
| added = Nov 12th, 2013 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
The problem is that our -set.xml files only encode one aircraft state (usually cold-and-dark). To encode (accurately) engines-running or in-flight as the start state, needs some kind of profile system where properties can have different values, and XML / Nasal can be initialised differently. That would make nice in-air starts possible (gear already up, throttles at sane position), as well as offering 'cold, dark and parked' or 'on the active and ready to go' as options. (And end all the per-aircraft 'auto-start' menu options - since they'd become standardised). <ref> {{cite web | The problem is that our -set.xml files only encode one aircraft state (usually cold-and-dark). To encode (accurately) engines-running or in-flight as the start state, needs some kind of profile system where properties can have different values, and XML / Nasal can be initialised differently. That would make nice in-air starts possible (gear already up, throttles at sane position), as well as offering 'cold, dark and parked' or 'on the active and ready to go' as options. (And end all the per-aircraft 'auto-start' menu options - since they'd become standardised). <ref> {{cite web | ||
| url = http://sourceforge.net/p/flightgear/mailman/message/30561002/ | | url = http://sourceforge.net/p/flightgear/mailman/message/30561002/ | ||
| Line 25: | Line 37: | ||
}} | }} | ||
</ref> | </ref> | ||