.

I am using the new Just Flight F28. Despite the initial axis assignments and saving them in AAO, when I restart the sim AAO fails to work as well as having assigned the axis from one device to a different device. For example, the ailerons are initially assigned and saved as CH Yoke. When I restart the sim, AAO sees it as an axis in CH Pedals. . The elevator axis, which is assigned to msfs control, works fine. I don't know why. The problem is erratic, so it's difficult to determine the cause. The buttons work fine, so I know that AAO is properly connected to the sim.

https://imgur.com/a/rXqDtck

I have noticed that if I double click in AAO assigned axis, the correct device is eventually recongnized. Essentially, when I first double click on an assigned axis, the wrong device shows up. I then close the window. When I double click on the same assigned axis a second time, the correct device appears. It happens only when I double click on the assigned axis the very first time. Also, the other axis appear to not have this issue. It's only the aileron assigned axis as it appears in the image.

Sounds strange, cannot say that I've heard that one before. What you are saying is, that you can assign an axis and it works, but the next time you (start your computer? start AAO?) they are no longer working because the assignment has changed on its own?

Couple of things:

- Unless something messes with the database files, AAO can't "forget". Make sure that there is no backup/restore/relocation tool running on your PC (like for example replicating your user files into OneDrive)

- AAO references the game controllers by their GUID that is assigned to them by Windows. The operating system changes those GUIDs for example when you replug the controllers into different USB ports = make sure that there is no faulty USB hub in play or something

- If you have a noisy potentiometer somewhere, that will always show up first. AAO can't help it when a device is constantly triggering even when you don't touch it. That is what the locking buttons are for, and there is an option on the Hardware menu where you can lock everything agains unwanted changes (so AAO will ignore the noisy device when you open an axis assignment to change it).

There are theoretically other strange things that could happen, like Windows assigning the same GUID to multiple devices, that would trip up AAO too. If all fails, send your proof of purchase and the AAO startup log to the support address (last page of the AAO manual).

Edited July 18, 20232 yr by Lorby_SI