The advantage of this approach is that the checklist files become the source of checklists, tutorials and autostart if the checklists change, so does the autostart (see Don't repeat yourself ). parsing errors).Īs of version 3.5, FlightGear can automate the execution of various sequences of aircraft checklists using the autochecklist.nas script in $FGDATA/Aircraft/Generic. Make sure to monitor the startup window and/or the Nasal Console loglist widget for any XML related warnings (e.g. Reload_checklist(filename: "777-200-checklists.xml") Ĭhange the filename to the name of the file you are editing. Var data = io.read_properties(checklist_path,"/sim/checklists") Var checklist_path=sprintf("%s/%s",getprop("/sim/aircraft-dir"),filename) You can set /sim/checklists/auto-tutorials=false to disable generating any tutorials at all.Ĭut and paste this little code snippet in the Nasal Console and excecute it: However, if your aircraft has custom tutorials, or it is not appropriate to have a tutorial for a particular checklist, you can disable this by setting false within the or. This is supported within the Checklist dialog, and also by the FG1000.īy default, checklists are automatically converted into tutorials. The plan is to extend this function so that checklists with one or more items containing a element can have an (optional) buttonĬhecklists can optionally be grouped together under a node in the property tree, with each group given a descriptive name. The element is exactly as you would expect - so property-assign, nasal etc. Clicking on the button executes the bindings, allowing the user to watch as the computer/co-pilot/instructor executes the checklist item. The checklist GUI displays items with such elements with an additional button. Conceptually, these are the actions that the user should execute to complete the item. One or more binding elements can be added to a checklist item. The following example shows a simple checklists XML file:įlightGear Aircraft Checklists PUI dialog Zero or more XML bindings that are used by the simulator to execute the checklist item if the user clicks on a ">" button next to the item.įor simple checklists the element can be omitted and entries placed directly under the.Note that this requires the marker model to be included in the aircraft model, as explained in the aforementioned article. This contains, , and sub-elements and uses the tutorial marker. An optional marker node that is used to display a circle around a control when the user clicks a "?" button next to the item.Incomplete checklist items are shown in yellow, while completed items are shown in green (NOTE: When more than one condition has to be met, the use of is mandatory to make this work). An optional condition node that evaluates when the checklist item is complete.It is recommended that the tags are kept short, to minimize the size of the displayed checklist. Second and and subsequent tags are displayed underneath each other. One or more values, to appear on the right hand side of the checklist.The item name, to appear on the left hand side of the checklist.One or more pages from the checklist, containing one or more of the following:.As the checklists may be quite long, it is recommended that they are put in a separate file using the following entry in the -set.xml file of the aircraft:Įach individual checklist is created under a XML tag, with the following sub-properties: Increasingly, the tutorials system is also extended such that it may make use of aircraft checklists.Ĭhecklists are situated under /sim/checklists. To learn more about creating custom checklists, see $FG_ROOT/Docs/ README.checklists and the Cessna 172P as the reference implementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |