@Black-Square I wish I had some real insight for you, but I don't. I own all of your planes except the Velocity. From the Dukes onward, I've used Axis and Ohs for control bindings, and it's always been a crap shoot. I always start with default MSFS events and vars to keep it as simple as possible. But every plane inevitably has some that don't work the way they should (or at least the way I expect), and that's the point where I dig into the assignments listed in the manual. For any of those that don't work, I use the dev menu behaviors tool, and the Axis and Ohs "watch simulator events" dialog. But they both have their own failings: the behaviors tool doesn't always list bindings, so I have to inspect the code displayed and try to glean what I can do from that. And the simulator events dialog sometimes displays native events that are being triggered by code -- and often I can't bind those events directly and the dialog doesn't indicate what to use. There are a couple other tricks I use in Axis and Ohs, and I'm always learning. For example, just a couple days ago, I discovered I can use to program virtual button presses on an axis I create (for the Just Flight F28, where the fuel levers are seemingly not on an axis).
Needless to say, due to the trial-and-error nature of this process, it sometimes takes a couple hours for me to bind a single plane, but it'd be awesome if I could just import an already existing control profile and have most of the assignments work out of the box.
Usually I start by binding just enough to get into the air, fly until I want to switch to autopilot, and then do the rest while the plane hums along happily on its own lol
