MV-22 button mapping for auto hover?

Autohover can't be easily mapped since it's not using any of the variables set by default by MSFS. Let me take a look at how can you map it and get back to you.

Thanks. I'm usually really busy trying to stabilize the osprey which makes it difficult to reach for the mouse, move it to the button, and press it without violating the autohover parameters. A button at my fingertips would be much easier. I look forward to your reply.

Note that I'm using Axis and Ohs to program my HOTAS so if there's a series of variables I could script then that would work for me.

I managed it with the following code. I scripted the code with AAO and assigned it to a button. I'm not 100% sure if this is completely correct, but it works for me (animation and function).
1 (>L:MARYADI0151, enum) 0x1109D (>L:EVENTS_ID, enum)

You need the hex code for the function and the MARYADI-VARS for animation. You also can toggle the animation and if you want, you can add that also. f.e. the autopilot.
1 (L:MARYADI0107, enum) - (>L:MARYADI0107, enum) 0x1107B (>L:EVENTS_ID, enum)

Or with a SPLIT (for the real push Effekt) - maybe WAIT is better here
1·(>L:MARYADI0107,·enum)·(SPLIT:100)·0·(>L:MARYADI0107,·enum)·0x1107b·(>L:EVENTS_ID,·enum)

The best Idea for your Hardware and the animation in AAO ist to map the key-down and key-up event with 1 and 0. That's the most elegant.

I made a Stream-Deck profile for the complete AP-functions and want to give it to flightsim. The only thing that is missing is the LED-Light for the availability of the hover mode (depending on wind, altitude and speed). You know what I mean? Sorry, my english is not the best. Maybe someone can help?

Edit: Found it. SOrry.

We are currently working on mapping autohover to a default AP variable on MSFS so it's easier for anyone to program it on their hardware.