Startup Profiles: Difference between revisions

Jump to navigation Jump to search
Line 17: Line 17:




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 [[Aircraft-set.xml|-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/
   | title  = <nowiki>Re: [Flightgear-devel] Crazy usability suggestion of the day</nowiki>
   | title  = <nowiki>Re: [Flightgear-devel] Crazy usability suggestion of the day</nowiki>

Navigation menu