After working for over a year, AOA suddenly locks up when I click on the dropdown box to add a new button binding. AOA works find with installed templets. It worked fine with axis bindings. It only freezes when clicking one of the dropdown buttons, i.e., Key down, key up, etc. I am using the latest version: v4.1 b51.

I downloaded a new copy from Just Flight and installed it after removing AOA via Control Panel. Still nojoy. I cannot find a support page on Lorby's site and the Just Flight support is only for installation issues, so I am here. I can use FSUIPC or SPAD.Next to bind the buttons, however, I am trying to centralize with AOA.

Thanks,

John

17 minutes ago, jmig said:

suddenly

These things don't just happen, there must be a reason. Did you get new any new hardware?

In AAO go to "Hardware->Device Blacklist". 

Move everything into the list on the right with the "Ignore" button that isn't a game controller that you want to use with AAO. This includes all keyboards, mice, all the HID devices, Saitek Panels, the StreamDeck and whatnot. They all have to go. Leave only proper joysticks, yokes, rudders, TQs on the left.

Restart the app after you did this.

Edited March 12, 20242 yr by Lorby_SI

18 minutes ago, jmig said:

I cannot find a support page on Lorby's site and the Just Flight support is only for installation issues, so I am here.

This here is the official support forum. And on the last page of the AAO manual you will find a support email address.

1 hour ago, Lorby_SI said:

These things don't just happen, there must be a reason. Did you get new any new hardware?

In AAO go to "Hardware->Device Blacklist". 

Move everything into the list on the right with the "Ignore" button that isn't a game controller that you want to use with AAO. This includes all keyboards, mice, all the HID devices, Saitek Panels, the StreamDeck and whatnot. They all have to go. Leave only proper joysticks, yokes, rudders, TQs on the left.

Restart the app after you did this.

Thanks Lorby. The only new device is a Meta Quest 3 headset. Is it possible AOA picked up the controllers and they are interfering? 

1 hour ago, Lorby_SI said:

These things don't just happen, there must be a reason. Did you get new any new hardware?

In AAO go to "Hardware->Device Blacklist". 

Move everything into the list on the right with the "Ignore" button that isn't a game controller that you want to use with AAO. This includes all keyboards, mice, all the HID devices, Saitek Panels, the StreamDeck and whatnot. They all have to go. Leave only proper joysticks, yokes, rudders, TQs on the left.

Restart the app after you did this.

That didn't help. I removed everything, in steps, until all I had left was the Honeycomb Alpha. It still killed AOA. 

1 hour ago, jmig said:

That didn't help. I removed everything, in steps, until all I had left was the Honeycomb Alpha. It still killed AOA. 

Reading your OP again, you seem to have messed up the events, variables or scripts database somehow. No idea how that would be possible, but it certainly looks the part. 

You can reset AAO to factory defaults by deleting the folders associated with the app. The uninstall will not do that (otherwise you might lose all data with a simple update). Check the chapter "File handling" in the AAO manual. This chapter will also tell you how to take a few steps back and maybe load a previous config that was still working. But that is only possible when you haven't overwritten all 6 backup generations already.

If wou were to delete the main config folder here

C:\Users\...\AppData\Local\LORBY_SI\LorbyAxisAndOhs*
(* would be the simulator you installed it for, nothing, MSFS or XPLANE)

the app will probably start working normally again - but you will lose everything. Alternatively try to find the error message that Windows hopefully put into the Application Event Logs when it decided to shut down the app and send it to the support mail address (last page of the manual). Please remember to include your proof of purchase.

 

 

Edited March 12, 20242 yr by Lorby_SI