20,741
edits
Talk:Aircraft checklists: Difference between revisions
Jump to navigation
Jump to search
m
→Checklists & Autostart: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html
m (→Checklists & Autostart: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html) |
|||
| Line 1: | Line 1: | ||
== Checklists & Autostart == | == Checklists & Autostart == | ||
'''Hooray:''' Based on the end user feedback we've seen on the forums, the autostart feature is another popular (read: important) thing for new users. And that's obviously something else which isn't currently standardized: autostart is implemented in a custom fashion for each aircraft. But using the new checklist system, it would probably even be possible to streamline the implementation of autostart features, simply by providing the raw, properties/scripts, that need to be processed in order to do an autostart. That would mean that autostart could be implemented on top of the checklist system, because it would also use a common/shared XML file that exactly describes how to perform an autostart step-by-step. These steps would then be detailed in the checklist itself - but given that not just the human-readable descriptions are provided, but also the simulator-related actions to perform, an autostart feature could be automatically provided for aircraft that have a full checklist implemented. At that point it would even be possible to add a button to each checklist item to interactively view the necessary step, and perform them just by clicking a button, including other checklists (landing, go-around etc). According to the git logs, [[User:Zakalawe]] has recently added state machine support - so that adding an autostart framework on top of the checklists system would seem feasible. | '''Hooray:''' Based on the end user feedback we've seen on the forums, the autostart feature is another popular (read: important) thing for new users. And that's obviously something else which isn't currently standardized: autostart is implemented in a custom fashion for each aircraft. But using the new checklist system, it would probably even be possible to streamline the implementation of autostart features, simply by providing the raw, properties/scripts, that need to be processed in order to do an autostart. That would mean that autostart could be implemented on top of the checklist system, because it would also use a common/shared XML file that exactly describes how to perform an autostart step-by-step. These steps would then be detailed in the checklist itself - but given that not just the human-readable descriptions are provided, but also the simulator-related actions to perform, an autostart feature could be automatically provided for aircraft that have a full checklist implemented. At that point it would even be possible to add a button to each checklist item to interactively view the necessary step, and perform them just by clicking a button, including other checklists (landing, go-around etc). According to the git logs, [[User:Zakalawe]] has recently added state machine support - so that adding an autostart framework on top of the checklists system would seem feasible. | ||
{{cquote| | |||
On a related note, I've been wondering whether we should start the sim with the engines running when starting from a runway. Being on the runway with the engine off isn't particularly realistic. If we were feeling particularly keen also having the altimeter set and the radios tuned to the tower frequency might be nice. | |||
: Ah, that's a much more contentious one. The problem, from my point of view, 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://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html |title= Crazy usability suggestion of the day|author=James Turner |date= Tue, 05 Mar 2013 03:39:23 -0800}}</ref>|James Turner}} | |||
<references/> | |||
== Canvas based Checklists == | == Canvas based Checklists == | ||