This issue seems to have started with updating to latest AAO (4.20 b43) and/or StreamDeck plugin (35.02).

 

When MSFS is the selected foreground application, "Lorby-SI AxisAndOhs" button presses will have a varying response time in MSFS from no delay to no response at all.

If another application is selected so that MSFS is no longer the foreground application, there is never a delay.

 

This issue is not occurring with other Stream Deck plugins (Flight Deck, Flight Tracker, etc.).

1 hour ago, egreiff said:

This issue is not occurring with other Stream Deck plugins (Flight Deck, Flight Tracker, etc.).

That is not a valid comparison. These plugins are C++ SimConnect clients in their own right. The AAO plugin is instead simple Javascript, that is first communicating with the AAO WebAPI, and AAO is then the SimConnect client talking to the simulator.

For the sounds of it, something in your simulator is compromising the AAO WebAPI, or AAOs SimConnect connection. Somehow. No idea. It doesn't really make any sense. Double check that you are not streaming the SD contents (C:\Users\...\AppData\Roaming\Elgato\StreamDeck\Plugins\com.lorbysi.aao.sdPlugin\streamingSettings.js - STREAM_IMAGES_TO_AAO set to false). Maybe turn off the AAO panel in MSFS.

Sorry that I can't tell you more, but as of today you are the only one who has this problem. I have no reference and no clue as to how this should be possible.

On a side note - IMHO it is not a good idea to run several programs at the same time that do essentially the same thing. (=SPAD, FSUIPC, AAO, FlightTracker, FlightDeck - etc.).

Edited June 22, 20241 yr by Lorby_SI

Thanks for the reply.

Streaming is off.

I'll work on the WebAPI as the issue and see if I can figure anything out.

As a SimConnect client, AAO works perfectly with all my other controllers (Honeycomb alpha/bravo, rudder pedals, Winwing FCU) at the same time that the Stream Deck is not communicating well.

Which port(s) are you using for the WebAPI? 

I was on port 6080 which I have been on for a long time. I just switched it back to the default 43380.