2,561
edits
m (adding screenshot to show custom autopilot dialog implementations) |
|||
Line 15: | Line 15: | ||
So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation. | So it is possible to write a custom <tt>autopilot.xml</tt> to override the generic autopilot implementation. | ||
This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both. | This custom autopilot configuration file can be driven by either the standard autopilot dialog, custom cockpit panel hotspots or a combination of both. | ||
Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in CVS/HEAD). | Also, it is possible to provide enhanced or completely new implementations of the standard autopilot dialog to cater for autopilot/aircraft-specific features (for examples, see the b1900d or Citation Bravo in CVS/HEAD). [[Image:Custom-autopilot-dialog.png|thumb|300px|A custom autopilot dialog]] | ||
Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots). | Some aircraft in FlightGear however only provide one means of interacting with the autopilot (i.e. autopilot dialog '''or''' panel hotspots). |
edits