Hello! This is my first post, so I hope I’m doing this right.
I recently purchased the new A2A Comanche and having trouble getting it setup with AAO. Even binding the basic axis like throttle, mixture, and prop it doesn’t seem like any of the binding options in AAO work. In the in-game binding, I need to choose the generic “Propeller” vs “Propeller 1” binds but don’t see these in AAO.
Further more, I noticed A2A has an external keybind utility so does this mean I can’t work it with AAO? I have all my controls setup in AAO and I love that.
I just bought the Comanche and am very interested to see what SPAD can control. And what it can’t…
This may be the only plane in my hangar that I won’t have a SPAD profile for.
Thank for these but unfortunately they don’t solve my problem, which is the axis binds. These are nice for button binds, though a lot of them I had already figured out, as it was just a matter of finding the variables used.
What I don’t understand is how to get the axes working. Like for example, in the MSFS binding it is “Throttle”, not “Throttle 1” or “Throttle 2”, etc. But in AAO the only options are the numbered throttles, not the “un-numbered” one.
Ok I finally figured this out. You need to use the Simulator Events for the axes. I originally thought those were only for buttons.
Throttle is THROTTLE_AXIS_SET_EX1 (There is another one that also half works, but won’t move the full range. Use this one!)
Propeller is PROP_PITCH_AXIS_SET_EX1
Mixture is AXIS_MIXTURE_SET
Hi, I’m not very smart with some of this. I don’t know anything about AAO, but I use Spad.Next because of my Class Echo. (I use it for my Logitech panels too, for convenience) I use the in sim settings for my Alpha and Bravo. I’ve seen you post this link here and on the A2A forum, but I’m unsure of what it does or how to use it. Is this specific to AAO? I’m not very fluent with Spad, as I usually just grab online profiles for the Class Echo from within Spad.Next itself. (I sure this isn’t for the Class Echo, but I’m trying to figure out how to control the AP with any of my hardware options)
It’s a SPAD profile. Go to the SPAD page that lists the profiles, and you should see a button to open the profile folder. Copy my file in there. You may need to relaunch SPAD for it to see it.
Thanks very much for sharing - just bought the Comanche this week and was baffled by that exact same thing! And now I also finally know how to fix the yoke in the JF BAe146…
MSFS often prefers the Events over the Axis Variables - that is true for almost every aircraft.
The most relevant flight control axis events are duplicated in a special group “!! Flight control axis” right at the top of the event tree, so you don’t have to search for them.
Those are not related to the SDK variables or events. The names sound similar, but the MSFS controller logic is a completely separate module from the SDK (which external controller apps have to use)
