I purchased the Black Square Analog Baron and had the mixture levers on my Honeycomb Bravo Throttle Quadrant bound to the L:BKSQ_MixtureLeverPosition_1, Number (and _2) LVARS with an Axis min of 0 and and an Axis max of 100. This was working well, I believe, until I installed the v3.0 upgrade. When it was working, the 0-100 values were evenly distributed across the full range of the mixture lever movment. Now, the 0-100 range is exhausted by just a small movement of the lever. Is anybody else experiencing problems with axis min/max scaling?

 

 

6 hours ago, geoffda said:

Is anybody else experiencing problems with axis min/max scaling?

No.

Can you post a screenshot of your current axis assignment?

I was just about to post with the same problem.
The usable range of my controller axis seems to have been cut in half.
With say one of my controllers set to throttle 1 and the end points adjusted with the AAO blue triangles (if necessary)
I have to move the controller arm about half way forward before I see the virtual throttle move in the sim
and the engine respond.
Happens with both my Thrustmaster Hotas and GoFlight quadrant.
Neither has a problem if I assign directly in MSFS.
A workaround to get the full range in sim is to set the Change Axis Assignment
Input Ranges Center to 0% rather than the default 50%.

Some screenshots:
https://www.dropbox.com/s/atm4e3tm48uyzl1/AddAxis.PNG?dl=0
https://www.dropbox.com/s/jsde4to6214nsyi/Change.PNG?dl=0
https://www.dropbox.com/s/nswr7ep9mjplhgv/RawMax.PNG?dl=0
https://www.dropbox.com/s/bmjpfjvtid6kiin/RawMin.PNG?dl=0
https://www.dropbox.com/s/gcik7h9y0hqa8yu/Throttle1.PNG?dl=0

 

A few observations:

1. MSFS prefers the Axis Events over the Axis Variables (second box from the top). For throttles try "THROTTLEn_AXIS_SET_EX1"

2. Every aircraft model handles these differently. It is entirely possible that the aircraft model only uses the "upper half" of the value range of an axis. In that case you move the red triangle towards one of the edges (or change Axis Min and Max to reflect this)

3. The blue and read triangles handle the INPUT range of an axis.

4. The Axis Min/Axis Max value handle the translation of the input values to what is sent to the simulator event or variable. Axis Min and Max are the most important parameter in this whole construct.

5. No two aircraft are alike. Throttles may behave totally differently between two different aircraft. So in this case it would be important to know what aircraft this is happening with

6. What AxisAndOhs does over SimConnect has nothing whatsoever in common/to do with with what you can assign in the simulator. These are two completely different mechanisms and cannot be compared to each other.

Edited April 10, 20233 yr by Lorby_SI

@gboz

The sim default AXIS events do not work on this airplane. The event code is in the xml but the scaling is broken. 

Instead I left the axis range to be default -16384 to 16384 and called this script from the Honeycomb axis.

There are two types of aircraft with Turbo and non differentiated by the creator variable.

Turbo range is 0 to 100, non-turbo is 0 to 16384 

(L:Bonanza-MixtureAll)·16384·+·2·/·s0·(L:BKSQ_Turbocharged,·bool)·
if{·l0·163.84·/·(>L:BKSQ_MixtureLeverPosition_1,·percent)·}·
els{·l0·(>K:MIXTURE1_SET)·}

 

10 hours ago, Lorby_SI said:

A few observations:

1. MSFS prefers the Axis Events over the Axis Variables (second box from the top). For throttles try "THROTTLEn_AXIS_SET_EX1"

2. Every aircraft model handles these differently. It is entirely possible that the aircraft model only uses the "upper half" of the value range of an axis. In that case you move the red triangle towards one of the edges (or change Axis Min and Max to reflect this)

3. The blue and read triangles handle the INPUT range of an axis.

4. The Axis Min/Axis Max value handle the translation of the input values to what is sent to the simulator event or variable. Axis Min and Max are the most important parameter in this whole construct.

5. No two aircraft are alike. Throttles may behave totally differently between two different aircraft. So in this case it would be important to know what aircraft this is happening with

6. What AxisAndOhs does over SimConnect has nothing whatsoever in common/to do with with what you can assign in the simulator. These are two completely different mechanisms and cannot be compared to each other.

Thanks for the reply.

My half throttle problem was happening with every plane I tried until I got to one that has reverse thrust range on it's throttle.
In this case just using Select Simulator Axis Throttle 1 gave forward thrust to one half of the controller and reverse thrust to the other.
Looks like on planes with no reverse thrust one half of the throttle is just being ignored if assigned by AAO as Throttle 1.
Is this really the expected behavior?

Good news is that using THROTTLEn_AXIS_SET_EX1 works as expected giving full range to the throttle in the sim.

8 hours ago, gboz said:

Is this really the expected behavior?

Yes. The value range of the variable is -1.0 to 1.0. The way the developers made it (apparantly) is, that negative values are reverse, positive are forward thrust. Or that they didn't "make" anything and this just is how the plane (accidentally) reacts when the variable is changed. This is not the same as operating the Events.

You could also just pull the red triangle to one side (as shown in the very early AAO video and as is mentioned in the manual too)  - or change Axis Min / Max as desired (for example, when it normally is -1.0 to 1.0 you would set 0 to 1.0 instead. Then the entire axis is translated to positive values only)

Edited April 11, 20233 yr by Lorby_SI

15 hours ago, Lorby_SI said:

Yes. The value range of the variable is -1.0 to 1.0. The way the developers made it (apparantly) is, that negative values are reverse, positive are forward thrust. Or that they didn't "make" anything and this just is how the plane (accidentally) reacts when the variable is changed. This is not the same as operating the Events.

You could also just pull the red triangle to one side (as shown in the very early AAO video and as is mentioned in the manual too)  - or change Axis Min / Max as desired (for example, when it normally is -1.0 to 1.0 you would set 0 to 1.0 instead. Then the entire axis is translated to positive values only)

Thank for the help, but still sounds a bit weird.
Problem also happens with Propeller and Mixture axis.
Don't see any logic in providing Mixture reverse zone
unless the sim just cannot differentiate axis.
Anyway everything working ok at the moment.

4 hours ago, gboz said:

Don't see any logic in providing Mixture reverse zone

There is no inherent logic and there are no rules. The +/- thing has nothing whatsoever to do with "reversing" anything. The value range is just a property of the variable or event. 

The events and variables will have the value range that is described in the MSFS SDK documentation, because the lists in AAO are generated programmatically from that spec. When Asobo says that the range is -16383 to +16383 then this is what AAO will apply when you select that event. That does not mean that the actual plane has to use the full range for anything. The event might not work at all, or just a portion of the value range might. There are aircraft that don't react to any SDK "thing" and control everything with custom LVars and BVars. That is just how things are in MSFS. After the initial trouble with the SDK, aircraft developers apparently prefer to go fully outside the box over adhering to the SDK.

The recommended course of action is to try the Events first (the second box from the top on the Axis Assignment dialog). That seems to be the MSFS default. FSX and P3D on the other hand seem to prefer the variables (=the box at the top).

Edited April 12, 20233 yr by Lorby_SI