177
edits
Autopilot configuration reference: Difference between revisions
Jump to navigation
Jump to search
→Adding a configuration to an aircraft: Add note why some autopilot configs have certain indices, and some not.
Chris blues (talk | contribs) |
Chris blues (talk | contribs) (→Adding a configuration to an aircraft: Add note why some autopilot configs have certain indices, and some not.) |
||
| Line 54: | Line 54: | ||
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. | ||
{{note|While the above seems to be the recommended standard, it has occasionally lead to trouble, not to index | {{note|While the above seems to be the recommended standard, it has occasionally lead to trouble, not to index additional autopilot configurations. Anyway, it shouldn't hurt to do so.<br> | ||
FG first loads generic configs, which get indexed atomatically as they appear. Then you override these generic configs with your own, which may lead to strange behaviour, if you for example overwrite the weather rules with an autopilot-helper configuration. Not only will you have no weather anymore, but also 2 systems that will most likely overwrite each others results all the time. Check the property-tree at <code>/sim/systems/autopilot[*]<code>}} | |||
=== Adding a property-rule configuration === | === Adding a property-rule configuration === | ||