Hi guys,

 I downloaded AAO yesterday and have encountered an issue when binding my VPF Rhino stick base using a Virpil VFX grip for MSFS2020. Hopefully it's just something obvious I'm missing as a new user..

I'm trying to bind the stick's hat switch to the:

ROTOR_LATERAL_INC

ROTOR_LATERAL_DEC

ROTOR_LONGITUDINAL_INC

ROTOR_LONGITUDINAL_DEC events.

I can create the bindings okay, and with the "Change button assignment" window open AAO recognizes the hat switch (it changes in the "Assigned button/key" field when I move the switch) but after I close that dialogue and go back to the main screen AAO no longer registers pushes from the buttons. When I move the hat switch the green light on the assigned buttons doesn't come on and MSFS doesn't register the control input.

Is anyone able to provide any suggetions?

 

Kind regards,

Butch

27 minutes ago, ButchNZ said:

I downloaded AAO yesterday

So you are using the DEMO version to check out your hardware before purchasing the app? 

27 minutes ago, ButchNZ said:

Is anyone able to provide any suggetions?

Not really, no. I'm not familiar with that hardware. The only reason for button LEDs not lighting up would be when you've assigned a Combo button and that isn't active at the moment.

Also, make sure that those events really do what you think they should do. They are the default events from the MSFS SDK - and aircraft developers are not obliged to use them. In fact, many don't, and you have to use IEs instead. Or find out whatever is required to achieve the effect that you are looking for.

In general, when you have issues like this in the DEMO version, don't buy the app. Retail and DEMO versions are functionally identical. When the DEMO doesn't work properly with your hardware, the retail won't do any better.

Edited January 16, 20251 yr by Lorby_SI

Hi mate. No, I've grabbed the full version, this is just the first aircraft I've had to bind this function with so it's the first time I've encountered the issue. it's not the end of the world if I can't get this specific function working as the rest of my setup is complicated enough that I still get enough benefits from using the software elsewhere.

 I don't have any combo buttons assigned  on these functions. As it stands I've just left the four cyclic trim binds assigned in msfs and it works, it'd just be tidier if I could get it all working through AAO.

13 hours ago, ButchNZ said:

 I don't have any combo buttons assigned  on these functions. As it stands I've just left the four cyclic trim binds assigned in msfs and it works, it'd just be tidier if I could get it all working through AAO.

I was trying to find out if the input from the joystick isn't coming in - as opposed to the events themselves not working.

Be mindful that the SDK events are not the same as the MSFS controller assignments, those two are not related. The names sound similar, but these are completely different logics. The difference is the same as ordering a ready made burger at McD's (=MSFS controller assignments) and buying the ingredients and cooking it yourself (SDK = AAO). The assingments in AAO are on a much lower level, and some investigation is required to make sure that the assignment that you do can actually work.

Did you try those buttons with an event where you do know that it is working? (Lights, Gear, something obvious). To make sure that AAO can work with this hardware.

Edited January 17, 20251 yr by Lorby_SI

Yes, I tried using the same hat switch on the Rhino for the BATTERY_MASTER_ON/OFF events which I had set to a switch on my Winwing Orion Throttle and working. Same result, AAO detects the inputs from the Rhino in the "Change button assignments" window, but after that window is closed it doesn't seem to, the LED stays off and the events don't fire.

7 hours ago, ButchNZ said:

Same result, AAO detects the inputs from the Rhino in the "Change button assignments" window, but after that window is closed it doesn't seem to, the LED stays off and the events don't fire.

Very strange. That makes no sense. Since both the assignment dialog and the normal operation are using the same logic, there is no reason why this should happen. No idea, sorry, never heard of something like this before. I know that Virpil controllers in general are problematic for AAO, because apparently they were made for the XBox and are actually game pads, not joysticks. But in the past people were always able to get them working somehow (by changing the "mode" of the device?).

This again shows how important it is to heed the note in the product descriptions in the shops - go and try the DEMO first, make sure that your hardware is fully supported.

But since this is so weird, I'll make an exception - if you want, send me your proof of purchase to the support address (on the last page of the AAO manual). Maybe we can figure this out somehow, not sure.

Edited January 18, 20251 yr by Lorby_SI

Yeah no worries. Possibly relevant- it's not a Virpil device per se, it's a VPForce device that's compatible with Thrustmaster/virpil/winwing grips. Shows up as a VPForce Rhino in Windows.