20,741
edits
Startup Profiles: Difference between revisions
Jump to navigation
Jump to search
→Status
(→Status) |
|||
| Line 6: | Line 6: | ||
== Status == | == Status == | ||
{{Note|as of 04/2016, a new proposal is being discussed on the FlightGear devel list}} | {{Note|as of 04/2016, a new proposal is being discussed on the FlightGear devel list}} | ||
James proposed, but didn’t yet have time to implement, a more formal ‘startup profile’ system for all aircraft, likely implemented as XML overlays on the basic -set.xml files. | |||
This would also solve the in-air start issues, to a degree. As was noted back in the original discussion, this raises some questions about initialising Nasal state and other dynamic systems (the FDMs already support in-air trimming, to various degrees), but James doesn't believe there issues are insurmountable, and the benefit in user experience would be very large - for novice users, for in-air starts, and more. | |||
It would help to know from the C172 team, what pieces would be needed /apart/ from an XML props overlay, to make the C172 do this as a standard feature? | |||
I would set a /sim/initial-config variable to a standard value: | |||
* ‘cold-and-dark’ | |||
* ‘engines-running’ | |||
* ‘circuit’ aka ‘takeoff' | |||
* ‘cruise’ | |||
* ‘approach' | |||
And this could be used to trigger whatever Nasal is needed beyond the property modifications. I imagine this proposal is too simplistic, but I need the aircraft developers to tell me in which specific ways that’s the case.<ref> {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34975108/ | |||
| title = <nowiki>Re: [Flightgear-devel] First-time user experience, | |||
and engine startup</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Mar 29th, 2016 | |||
| added = Mar 29th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
* add a /sim/startup/state string property | * add a /sim/startup/state string property | ||
* permit -set.xml files to supply states at /sim/aircraft/states[0..n] | * permit -set.xml files to supply states at /sim/aircraft/states[0..n] | ||