In AAO if I bind my Honeycomb Bravo flaps axis to AXIS_FLAP_SET on the iFly 737 MAX8, the flap lever will move through to full extension properly, but then it won't retract beyond the Flap 1 detent. iFly is using the Asobo ASOBO_HANDLING_Flaps_Lever template, so they aren't doing anything wierd. The flaps are definitely set at 1 even though the lever on my controller is fully up. The VC lever is at the flaps 1 detent, the flap gauge shows flaps 1, and that can be confirmed in the external view. The sim sees HANDLING_FLAPS at 12.5% when it should be 0. It is possible that the value might briefly go to zero and then bounce back, but I can't be certain. It definitely isn't oscillating. If I make the same binding directly through MSFS, the flap lever behaves properly.

The raw input that AAO says it is sending at the end of the axis is -16383 which is correct. When entered manually as p1 for AXIS_FLAPS_SET in the event debug window and executed (p0 is the previous flap lever position), the flap lever correctly moves to up. Since the bind works correctly in MSFS, I'm thinking that the problem is likely in AAO. I would assume if it were a software bug in the aircraft or a hardware issue, I'd be able to reproduce it with MSFS binds. Presumably, something that AAO is doing is causing the mouse rect for the lever to send incorrect input when the lever is at the end of the range. Anyway, I'm at a loss as to how to figure out why AAO is behaving differently. I didn't need to do anything other than set the bind in MSFS to make the lever behave, but I've tried deadzones and curves in AAO anyway. Nothing that I've tried worked. Any idea what might be going on or what further debugging I might try?

Edited October 18, 20241 yr by geoffda

10 minutes ago, geoffda said:

Any idea what might be going on or what further debugging I might try?

You cannot compare what the sim controller assignments are doing with what AAO is allowed to do through the SDK. While the names of the items in both sound similar, they are completely different "logics". That is why AAO will always behave differently, what it can do with the SDK has absolutely nothing to do with the MSFS internal assignments.

Did you try other flaps releated events? There is more than one. I will try and look into it, but my MSFS has become very unstable. I am barely able to start a flight, the sim CTDs before I get into the cockpit

Edited October 18, 20241 yr by Lorby_SI

I tried binding to the "Flaps Handle" sim axis, as well as the FLAPS_SET Flight Control Axis, but neither of those worked at all--that is, neither would trigger the VC flap lever to move. From the code, it looks like AXIS_FLAP_SET is correct; the input event seems to expect values on the range of -16384 to 16384.

Edited October 18, 20241 yr by geoffda

3 minutes ago, geoffda said:

I tried binding to the "Flaps Handle" sim axis, as well as the FLAPS_SET Flight Control Axis, but neither of those worked at all. From the code, it looks like AXIS_FLAP_SET is correct; the input event seems to expect values on the range of -16384 to 16384.

Put a detent on the lowest value? Also, make sure that Rounding is set to "int" for that value range.

As soon as I'm able, I will take a look at the behavior code. Sometimes the developers add a little extra in certain positions (like those extra "arm" LVars with the spoilers).

Edited October 18, 20241 yr by Lorby_SI

Yeah, I forgot to mention that I tried putting a detent on the lowest value as well. That didn't work. Thanks for having a look. 

Edited October 18, 20241 yr by geoffda

2 minutes ago, geoffda said:

Yeah, I forgot to mention that I tried that as well. Thanks for having a look. 

You mean you tried the detent? So the value is kept at -16383 when the axis is inside it? Do you have Tools->Axis advanced mode turned on?

Edited October 18, 20241 yr by Lorby_SI

OK, I was able to map this to the flaps lever on my Bravo. I needed two assignments:

1. the AXIS_FLAPS_SET event
2. the MSFS Input Event "HANDLING_Flaps"

For 1 I left a little gap to the left of the axis range by pulling the blue triangle a bit to the right. The assignment is otherwise standard, -16K to +16K, Rounding "int", reversed

Then I assigned the IE "HANDLING_Flaps" to the same lever, Axis min = 0, Axis max = 1, Rounding "int", reversed. I now fitted the entire assignment into the slot that I left in the first one, by pulling the red triangle and then the rightmost blue triangle to the left, so the ranges don't overlap.

The first assignment is actually controlling the flaps, and the second assignment just sets the lever to 0.

Edited October 18, 20241 yr by Lorby_SI

Edited October 18, 20241 yr by Lorby_SI

Thank you so much! That did the trick! How on earth did you figure that out? 

EDIT: Looks like I need to dig into what you are doing with the MSFS Input Events...

Edited October 18, 20241 yr by geoffda

7 minutes ago, geoffda said:

How on earth did you figure that out? 

Looked for Input Events first thing (they have their own section on the event selection dialog). After all, that is what developers are supposed to use (as far as I understand it). IEs are read at runtime from the aircraft, so I definitely know that they must do "something".  Tried a few values (using the script editor and the test button) to see if I could use only the input event, but it didn't agree with that. So I combined both.

This is not dissimilar to the spoilers construct mentioned earlier. Normally, I would expect the axis to cover the entire range, from disarmed - armed to fully up. But in many cases it is split in two.

Edited October 18, 20241 yr by Lorby_SI

You ar the best! Thanks again. I'm guessing you will have made quite a few people happy due to your efforts here. It would have never occurred to me to combine the two bindings like you did.

Edited October 18, 20241 yr by geoffda

4 minutes ago, geoffda said:

You ar the best! Thanks again. I'm guessing you will have made quite a few people happy due to your efforts here. It would have never occurred to me to combine the two bindings like you did.

Yes well. I think that many people don't know that you can assign any number of things to the same lever (or button) at the same time. With that technique you can also create non-linear response on a single axis. Or any number of crazy combinations, like automatically lowering the gear when the flaps are fully extendend. Etc.

Of course you can do the same with a single RPN script assigned to a single axis. Whichever you prefer. 

Edited October 18, 20241 yr by Lorby_SI