20,741
edits
Startup Profiles: Difference between revisions
Jump to navigation
Jump to search
m
begin de-quoting
No edit summary |
m (begin de-quoting) |
||
| Line 2: | Line 2: | ||
{{Note|Also see the new [[Aircraft-set.xml#Variants_.283.6.2B.29|<tt><nowiki><variant-of></nowiki></tt> tag]] which could be used for this}} | {{Note|Also see the new [[Aircraft-set.xml#Variants_.283.6.2B.29|<tt><nowiki><variant-of></nowiki></tt> tag]] which could be used for this}} | ||
{{ | == Background == | ||
| | |||
In-air starts are problematic, but fixing this is a Bigger Problem (TM) which I may take a look at after the release. (Probably means extending the -set.xml files to overlay different property states when starting in-air) | |||
<ref>{{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34640695/ | |||
| title = <nowiki>[Flightgear-devel] Launcher changes for 3.8</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Nov 23rd, 2015 | |||
}}</ref> | |||
The challenge (perhaps) is that many aircraft authors have modeled the complex startup procedures of their aircraft. Try starting the AN-2 for instance ... it's quite a procedure (fortunately the tutorial walks you through the steps.) As our systems modeling gets better and better it may be harder and harder to be able to initialie each aircraft with the engine(s) running. | |||
<ref> {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/24944252/ | | url = http://sourceforge.net/p/flightgear/mailman/message/24944252/ | ||
| title = <nowiki>Re: [Flightgear-devel] Issue with default starting scenario</nowiki> | | title = <nowiki>Re: [Flightgear-devel] Issue with default starting scenario</nowiki> | ||
| Line 11: | Line 20: | ||
| added = Apr 6th, 2010 | | added = Apr 6th, 2010 | ||
| script_version = 0.25 | | script_version = 0.25 | ||
}} | }}</ref> | ||
}} | |||
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. | |||
<ref>{{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> | |||
| date = Nov 23rd, 2015 | |||
}}</ref> | |||
{{FGCquote | {{FGCquote | ||
| Line 26: | Line 43: | ||
}} | }} | ||
{{FGCquote | {{FGCquote | ||