20,741
edits
Talk:Aircraft checklists: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→Checklists & Autostart + limits.nas: http://flightgear.org/forums/viewtopic.php?f=25&t=19836#p182372) |
No edit summary |
||
| Line 1: | Line 1: | ||
== Reloading == | == Reloading == | ||
is there any way to reload the checklist without restarting flightgear [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39799.html] | is there any way to reload the checklist without restarting flightgear [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39799.html] | ||
== Checklists and Replay == | |||
With ThorstenB's work on allowing [[Instant Replay]] flights to be saved via the flight recorder subsystem detailed in [http://gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder $FG_ROOT/Docs/README.flightrecorder] and flights to be continued at a later time, it would seem like a good idea to consider making the replay system aware of checklists supported by the aircraft, so that different aircraft/cockpit configurations can be applied. Supporting such a use-case would drastically improve turnover rates at events like FSWeekend or LinuxTag, i.e. when demonstrating FG to new users. Basically, we would need a way to completely reset the aircraft to a predefined state and then apply a certain checklist. | |||
== Checklists & Autostart + limits.nas == | == Checklists & Autostart + limits.nas == | ||
'''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 [http://flightgear.org/forums/viewtopic.php?f=25&t=19836#p182372]. 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 [http://flightgear.org/forums/viewtopic.php?f=25&t=19836#p182372]. 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. | ||