20,741
edits
Talk:Aircraft checklists: Difference between revisions
Jump to navigation
Jump to search
→In-air startups & supporting Startup Situations
m (→In-air startups & supporting Startup Situations: should probably be moved to a separate article ...) |
|||
| Line 30: | Line 30: | ||
| url = http://sourceforge.net/p/flightgear/mailman/message/34640695/ | | url = http://sourceforge.net/p/flightgear/mailman/message/34640695/ | ||
| title = <nowiki>[Flightgear-devel] Launcher changes for 3.8</nowiki> | | title = <nowiki>[Flightgear-devel] Launcher changes for 3.8</nowiki> | ||
| author = <nowiki>James Turner</nowiki> | |||
| date = Nov 23rd, 2015 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= Currently the entire -set.xml is overlaid on the property tree. I would extend this with additional overlays based on some ‘phase of flight value’, where the values are - cold-and-dark - pre-takeoff - cruise - approach It’s interesting to note the difference between ‘cold-and-dark’ and ‘pre-takeoff’ is essentially the same as what the existing auto-start functionality does in most aircraft. But this would simply be a set of property values. For anything which requires Nasal, I guess the aircraft scripts would have to check the value of /sim/presets/phase-of-flight and adjust things accordingly. (And there’s presumably lots of complexity there) I need input from aircraft authors on how feasible this is, of course. But the usability pay-off is potentially huge; standardised auto-start, nice in-air starts, easier setup of training configs. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34642417/ | |||
| title = <nowiki>Re: [Flightgear-devel] Launcher changes for 3.8</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | | author = <nowiki>James Turner</nowiki> | ||
| date = Nov 23rd, 2015 | | date = Nov 23rd, 2015 | ||