I have the H145 helicopter.  The collective position is shown on the main screen with a value of 0-10.

I also have a USB handbrake which is recognized by Windows and the sim.  Mapping the collective axis to the handbrake axis in the sim works as expected. Full range of motion of the handbrake stick results in full range of collective motion in the sim (0-10).

I can also use Axis and Ohs to do the same, and the "Move Joystick axis" shows the value from 0 to 65355 for the stick when moved.

- If I enter the min/max of 0 and 65355, the helicopter collective jumps to 5 as soon as I move the stick and the range is 5-10 in sim

- If I set the min/max to -65355 and +65355, the helicopter collective starts at 0 but doesn't change until the stick is midway through its travel and then it jumps to 5 and has a range of 5-10 on the upper half of the stick.

- If I set the min/max from 0 to 100, the collective jumps to 5 as soon as I move the stick and barely moves higher than 5.

This makes absolutely no sense to me.

What am I doing wrong? 

 

5 hours ago, Virtual-Chris said:

and the "Move Joystick axis" shows the value from 0 to 65355 for the stick when moved.

That is the physical value range of a Joystick Axis. It has nothing to do with what value is required in the sim - it is the "technical" INPUT value.

Axis Min and Max on the other hand determine the OUTPUT value. They must be set to whatever values the aircraft expects.
Common values are 0 to 1, 0 to 16383, -16383 to 16383. If you are using default K - events, then the value range can be found in the simulator's SDK documentation (and it will be one of the 8k/16k/32k values, K - events can't process floating point numbers). If it is an LVar, then the developer of the aircraft can tell you the value range.

AxisAndOhs then maps the input range of 0-65K onto the output range that you determine with Axis Min and Max (applying the curve, reverse, whatever). AAO is basically just a translator between DirectX/MIDI (=the real physical devices) and the simulator SDK (which has its own rules and value ranges).

Edited March 15, 20233 yr by Lorby_SI

3 minutes ago, Lorby_SI said:

That is the physical value range of a Joystick Axis. It has nothing to do with what value is required in the sim - it is the "technical" INPUT value.

Axis Min and Max on the other hand determine the OUTPUT value. They must be set to whatever values the aircraft expects.
Common values are 0 to 1, 0 to 16383, -16383 to 16383. If you are using default K - events, then the value range can be found in the simulator's SDK documentation. If it is an LVar, then the developer of the aircraft can tell you the value range.

AxisAndOhs then maps the input range of 0-65K onto the output range that you determine with Axis Min and Max (applying the curve, reverse, whatever). AAO is basically just a translator between DirectX and the SDK.

Is that explained anywhere? I read through the documentation and could not figure it out. What a waste of an afternoon.  At any rate, it’s easier to just use the sim. 😞

48 minutes ago, Virtual-Chris said:

 At any rate, it’s easier to just use the sim.

if you only have the one controller setup and if you don't want any of the other features of AAO, then yes - you will not need an app like this.

As it says in the product description, AAO is a replacement of the controller logic.
It is not related to the in-sim controller assignments in any way. It uses the SimConnect API to inject SDK and custom events and variables directly into the simulators processing. As do all the other tools of the same nature (SPAD, FSUIPC etc.), that is just how it works. And these variables and events are potentially different for every aircraft, that depends on what the individual developers did.

An app like this only becomes relevant if you want your controller setup to be different for every plane, or if you want to control things that aren't present in the simulators own assignments, or if you require the other features of the app (gauges, webapi, fmcs, bridges etc.).

btw. AAO sets the default min/max parameters for an axis event automatically when you create the axis assignemnt. If that doesn't work right away, then there is a good chance that the developer took a different route and you have to chase down the BVar, LVar or whatever he implemented for this. Or maybe he just uses a different value range from the default. 

Edited March 15, 20233 yr by Lorby_SI