I see A&O working but not doing anything in the sim. If you look at the app you can see the assigned axis working but when you run the MSFS sim they don’t work. Looks like some knid of sim connect issue I think since SU11. Seems like a lot of 3rd party stuff has been broken since that update. I am using W11 and logiteck throttle nothing special but although the assignment works it doesn’t work in sim - if I assign the axis in the sim (ie not in A&O) all works as you would expect, so something is not happening. I am using latest release  available from Simmarket.

 

 

17 hours ago, pilot101 said:

I see A&O working but not doing anything in the sim. If you look at the app you can see the assigned axis working but when you run the MSFS sim they don’t work. Looks like some knid of sim connect issue I think since SU11. Seems like a lot of 3rd party stuff has been broken since that update. I am using W11 and logiteck throttle nothing special but although the assignment works it doesn’t work in sim - if I assign the axis in the sim (ie not in A&O) all works as you would expect, so something is not happening. I am using latest release  available from Simmarket.

 

 

You are probably just assigning the wrong axis assets. If you had a SimConnect problem, AAO would not even connect (the green LED stays dark) and throw an error. You would not be able to even assign an axis in that state.

Be mindful that AAO and the controller assignments in the sim are not related. These are completely different "logics". AAO uses what is provided in the simulators' SDK. The internal MSFS controller logic obviously doesn't care about that. Which is why you can't assign the same "thing" both in AAO and in MSFS at the same time, they would fight eacht other.

This is always a trial&error process, because controls can be different for every single aircraft. First you try the simulator axis variables from the selection at the top. If those don't work, you try the axis events, using the second selector from the top (the most common axis events are grouped at the top pf the list in an extra group). etc.

For the record, AAO and all axis are working perfectly fine, even with the current MSFS beta version (1.30.9.0). As it is obviously doing for a couple of thousand other customers - there have not been any similar reports.

 

Edited January 9, 20233 yr by Lorby_SI

I have the same issue as the OG, poster after I migrated my database to a new PC. For the DA40, my throttles used to work with Axis throttle1 set. Buttons and everything thing else works fine. Maybe I needed to read lvars and Hvars from sim on the new PC? 
 

Thankyou for the fast response. what happened was I just changed from one controller - an old saitek trim wheel  to another axis on a logitech throttle. The Trim wheel was deceased. At that point the result as described above happened. Previously all worked very well. 

 

However, I re installed the latest version of the AAO product and all seems to be working again. Since I only use one axis (trim) and a 'bog standard' logiteck throttle I couldn't see why there was an issue and do not have a clue as to why this happened. I also use the Saitek HW for a switch panel which works well. 

 

anyway thanks again for your advice.

I think I found out why the AAO was not responding recently.

MSFS reloaded my default (backed up) controls recently due to a crash. Apparently this config had an axis for trim which is the only assignment I have in AAO. I noticed this had happened and deleted the MSFS assignment  and then found the AAO did not work. and couldn't get it to go as outlined earlier, however it turns out that if an assigned axis is deleted in the sim AAO does not pick it up until the sim is rebooted. Not something that you should do of course an AAO says to make sure not to have conflicting assignments, but just deleting them in sim does not necessarily allow AAO to just pick up the assignment without a reboot of the sim.

Anyway thats what i am seeing at present. So just posted in case this is an issue for anyone here.