I'm currently playing around with some of my Midi-Devices to use them as Controllers in MSFS using Axis and Ohs. I understand how to map Midi Buttons and Encoders (essentially also repeatedly pressed buttons) to Flightsim Events in your program, but I don't get how to map Midi Events to Axis like Throttle, Mixture etc. Lets say I want to assign a Hardware Midi-Volume-Fader to the Throttle Axis of my Plane. I'm using a Korg nanoKontrol Studio Device. In the assignment Dialogue I select "Throttle 1" from the "Select simulator axis" Dropdown. I then simply move the Fader on my Device and the nanoKontrol shows up in the "Device" Field, as well as an Entry "CHN:0 EVT: XXX" in the "Move Joystick Axis" Field, where XXX is a Value between 0 and 127 depending on the Position of my Fader. When I save this Configuration the Fader doesn't work as an Axis but - if it works at all - as a simple Button that switches the Throttle from zero to Full Throttle. 

So the question is: Can I map "non button like" Midi Controls, like Faders and "Potentiometers" (well, my "Pan" knobs on the midi-mixer) to Axis in the Simulator, and if yes, how can I do it?

 

Edited February 2, 20224 yr by theflyguy

33 minutes ago, theflyguy said:

"Move Joystick Axis" Field, where XXX is a Value between 0 and 127 depending on the Position of my Fader.

AAO expects the fader to send a single note (=the EVT part) with a velocity value between 0 and 127 (you won't see that displayed here). From what you describe, your fader is sending 128 different notes, that will never work with AAO.

So if for example I assign the fader on a Behringer X-Touch to an axis, I get a fixed "CHN:1 EVT:3009", and that EVT never changes while I move the control (=the fader is sending the same note, but with different velocities). If the fader is configured correctly in the X-Touch Editor.

Edited February 2, 20224 yr by Lorby_SI

Well I thought the Values between 0 and 127 ARE the Velocity Values. But anyway: With the rotary hardware inputs on my Controller (The PAN Knobs) it is like you describe. Here I get the same EVT Value in any Position of the "Potentiometer". I.e. its "CHN: 0 EVT: 3016" for the PAN Knob on Channel 1.  Anyway: This also doesn't work as an Axis when assigned in Axis and Ohs. 

EDIT: I found out that my MIdi Controllers has several operation Modes that can be switched by holding button combination while switching the device on. I found a Mode where also the faders work in a way that they only use one Midi Event in all Fader Poitions. Thank you for our imediate Reply. Everything is working now.

Edited February 2, 20224 yr by theflyguy

23 minutes ago, theflyguy said:

Anyway: This also doesn't work as an Axis when assigned in Axis and Ohs. 

It does for me... Are you sure that the assigned axis is working at all, did you check with a different controller? = I don't mean the knob on the MIDI device, I mean the throttle or whatever axis.

Actually - I do mean the rotary encoders too. I just remembered that I had dealings with Korg devices before. The rotary encoders may not be sending the full velocity range from 0-127, it is possible that they are configured like toggles (they only send 63-64-65, or 0 - 64 -127 depending on left turn - no turn - right turn. Or something like that). I think that I will include an input value display for axis in the next version of AAO, then you can see if the device is sending a proper value range or not.

Edited February 2, 20224 yr by Lorby_SI

The Jog-Wheel ist the only Encoder on this Device, and I can map it successfully to some MSFS Events, like ike Autopilot Altitude Setting. But there are still Problems with other Bindings. I.e. when I map the Autopilot Heading to the Jog-Wheel, I can only change the Heading 30° to the left and to the right of the initial Heading (North). Anyway, I have other Midi Devices with a lot more Encoders that already work very well with Axis and Ohs.