177
edits
Autopilot configuration reference: Difference between revisions
Jump to navigation
Jump to search
→Adding an autopilot configuration: add note about indexing the autopilot configurations
Chris blues (talk | contribs) (→Adding an autopilot configuration: add note about indexing the autopilot configurations) |
|||
| Line 34: | Line 34: | ||
<syntaxhighlight lang="xml"> | <syntaxhighlight lang="xml"> | ||
<autopilot> | <autopilot n="100"> | ||
<path>Aircraft/MyAircraft/Systems/my-autopilot.xml</path> | <path>Aircraft/MyAircraft/Systems/my-autopilot.xml</path> | ||
</autopilot> | </autopilot> | ||
| Line 45: | Line 45: | ||
<systems> | <systems> | ||
<!-- many other elements live here --> | <!-- many other elements live here --> | ||
<autopilot> | <autopilot n="100"> | ||
<path>Aircraft/MyAircraft/Systems/my-autopilot.xml</path> | <path>Aircraft/MyAircraft/Systems/my-autopilot.xml</path> | ||
</autopilot> | </autopilot> | ||
| Line 53: | Line 53: | ||
node of your <code>aircraft-set.xml</code> file. Note, that more than one <syntaxhighlight lang="xml" inline><autopilot></syntaxhighlight> node may be present, each will create a new instance of the autopilot subsystem when running FlightGear. They run in the order of appearance under <syntaxhighlight lang="xml" inline><systems></syntaxhighlight>. For example, lateral and vertical autopilot modes could live in separate files, as could a yaw-damper system. | node of your <code>aircraft-set.xml</code> file. Note, that more than one <syntaxhighlight lang="xml" inline><autopilot></syntaxhighlight> node may be present, each will create a new instance of the autopilot subsystem when running FlightGear. They run in the order of appearance under <syntaxhighlight lang="xml" inline><systems></syntaxhighlight>. For example, lateral and vertical autopilot modes could live in separate files, as could a yaw-damper system. | ||
While the above seems to be the recommended standard, it has occasionally lead to trouble, not to index the autopilot configurations. Anyway, it shouldn't hurt to do so. | |||
=== Adding a property-rule configuration === | === Adding a property-rule configuration === | ||