ATT and Spad.Next bind
-
In my experience so far, I have to use the AP_PITCH_LEVELER event twice, with a short delay in between. For some reason the first event sets the AP to GP, the second event sets it to ATT. Curious if others have noticed this? It seems that there may be more to having it set ATT directly with a single event? Or maybe not ... ?
-
Below follows the way it works for ATT ON/OFF.
ATT OFF
ATT ON
-
Unfortunately that does not work for me. Using AAO (which is only another way to define RPNscripts) I can enable the ATT mode but only without the automated setting of the att-Trim-wheel.
Any chance to get the variable/script which is executed when the ATT-Button in the cockpit is pressed (maybe also including the sounds played) ?
Thx -
@syff you've mentioned somewhere you're using my AAO templates for the Duke. Take a look at the
Duke_AP.tmpl
included there, it has bindings for most of the autopilot functions of the plane, including a workaround for the yoke CWS switch, it's using HC Bravo, but you can rebind them to anything you like, or just take inspiration how it's done.The upcoming Duke update will change some of these functions and I will adapt my templates accordingly, so keep in mind you may have to update those also :)
-