For the past month or so I have noticed controls mapped with AAO not working after flight restart.  Typical is axis.  AAO is connected and the axis moves in the AAO windows but not in the plane.  Nothing fixes except exit sim and restart. Exit AAO is not enough when stuck.   This is restart to runway and I have a habit of placing the controls in the default state (parking brake, throttle, etc) while sim is restarting. No sense zooming down the runway before I am ready.   So I have a hunch that AAO is sending sim events for my movements while flight is reloading and the communication is getting error and not recovered.  Probably on the sim side or the connector in community.   If I remember, I will close AAO before restart flight but I wondered if AAO can recognize the state "restart in progress"? Maybe not because the airplane does not change.

This is definitely not normal. What do you mean by "flight restart" exactly?

Axis are usually directly transmitted through the simulators own SimConnect API. The module in Community is only there for LVars. 

1. Try connecting AAO only when you are already sitting in the cockpit, not while the simulation is loading.

2. Avoid external camera views until AAO shows that it has recognized the plane. Stay in the cockpit. That is the state that AAO is looking for. The simulator events for "aircraft loaded" etc. are no good, because MSFS sends those at least three times while the simulation loads. There is nothing conclusive in the API to exactly determine the current state of the sim. (this is not a problem with the legacy sims, only with MSFS)

3. Check the AAO logfiles for USB errors coming from your hardware - that can cause the same behavior

4. Use "Hardware->Device Blacklist" and move all devices into the list on the right with the "Ignore" button that aren't game controllers that you are using with AAO:

5. No need to shut down and restart AAO. Just disconnect and reconnect (by clicking on the green LED in the menu bar)

6. When the title bar says "waiting for aircraft data" nothing is transmitted to the sim. Only when the aircraft title is shown there.

 

Edited March 1, 20233 yr by Lorby_SI

When flying, if you hit escape, one of the options is RESTART.

I had a guess that the problem was caused by moving controls during restart but I just did 5 tests and  and did not reproduce.

This is occasional lockup event requiring sim exit but I have not found procedure to reproduce.

The USB device is still connected and works fine in the axis windows.

Disconnect/reconnect has never fixed.  Exit/run AAO does not fix. That is why I think the hang is in sim core or connector.

The next time it occurs I will check the log.

 

 

 

 

 

1 hour ago, JJBZ53 said:

When flying, if you hit escape, one of the options is RESTART.

OK, I will check that. Most likely, this leads to another strange sequence of events in MSFS that are non-deterministic... and AAO can't understand when to connect. For example, on the way from the world map to the cockpit the sim sends "aircraft loaded" three times - how is an app supposed to know when the sim is actually ready...

But SimConnect is not known to react like this. Sounds strange. Are you in the Beta or is this trunk MSFS?