Hello:

I need help setting up a prop axis which includes feathering. The slider on my Joystick puts out 0 - 16384 and I need -4096 - 16384 but I can't seem to get the value to go negative. I feel certain there is a way to map this but I don't see how.

I would appreciate any assistance available. Thanks in advance.

Edited February 19, 20242 yr by The Artful Dodger
Needed notification.

On the Edit Axis Dialog you can enter/alter "Axis Min" and "Axis Max" to define the output range

Make sure that the output event can make use of that value range - check the MSFS SDK documentation

Edited February 19, 20242 yr by Lorby_SI

I see the Edit Axis RAW parameters but I don't know how to enter -4096 as the value to send to the simvar when the slider's value is 65535. I got the feathered value from the 'Watch Simulator Events', and moved the lever to the bottom of the feather range. The quoted value was 4294963246 which in binary is - 4096; the max was 16384.

So, the slider goes from 65535 => 0 So, I want 65535 to map to -4096 and 0 to map to 16384. I can change the Left margin only as low as 0. How do I force it to go negative?

44 minutes ago, The Artful Dodger said:

I see the Edit Axis RAW parameters but I don't know how to enter -4096 as the value to send to the simvar when the slider's value is 65535. I got the feathered value from the 'Watch Simulator Events', and moved the lever to the bottom of the feather range. The quoted value was 4294963246 which in binary is - 4096; the max was 16384.

So, the slider goes from 65535 => 0 So, I want 65535 to map to -4096 and 0 to map to 16384. I can change the Left margin only as low as 0. How do I force it to go negative?

You are looking in the wrong place.

Just doubleclick the axis assignment => the Edit Axis dialog opens. There you will find the "Axis Min" and "Axis Max" boxes, which define the output range.

There are two sides to this coin: INPUT and OUTPUT. AAO translates the input range of a device (0-64K for a joystick, 0-127 for MIDI, 0-32K for vJoy, 0-255 for a GamePad etc. etc - minus your margins, detents and deadzones, applying the curves etc. etc.) to the output range defined by the Axis Min and Axis Max boxes => which is then applied to the event/variable/whatever you have selected in the assignment..

Oh, and don't forget to set the "Rounding" parameter correctly ("float" for ranges between -1.0 and +1.0, "int" for all others that rely on integer numbers = the simulators K-Events)

 

Edited February 19, 20242 yr by Lorby_SI

To illustrate this further, here is an extreme example: the Condition Lever in the C208.

This lever has only three positions "0 - 1 - 2", technically it is not an axis at all. You cannot set it to any position between these three, not even with the mouse.

To operate it with a joystick axis (input range 0-64K) you select the "MSFS InputEvent" "FUEL_1_Condition_Lever" and then set "Axis Min" to "0" and "Axis Max" to "2", Rounding to "int".

Now you can assign a joystick lever and it will operate the Condition lever properly. 
 

Edited February 19, 20242 yr by Lorby_SI

AxisAndOhs Manual (click on the grey question mark icon in the top menu), Chapter 3.7.1 "Assign a new axis", the following page says "OUTPUT", note the yellow markings and the yellow box.

Edited February 19, 20242 yr by Lorby_SI

Never mind - I'll control it with SPAD!

28 minutes ago, The Artful Dodger said:

Never mind - I'll control it with SPAD!

??? What is to problematic about my explanation(s) and/or the AAO manual that you can't understand this process? Should it be explained differently, if so - how?

Edited February 19, 20242 yr by Lorby_SI

I think he is more familiar with SPAD and doesn't want to put effort in to learn Axis & Ohs' complex functions. I am the opposite. I bought SPAD, mainly for its ease of using Go-Flight device rotaries. However, I find it more complicated and time consuming to use than Axis & Ohs. 

I find that Axis & Ohs offers a good balance between ease of use and feature complexity.

 

 

 

 

 

.