I don’t think that this is specifically an AAO issue, but the app has completely stopped working for me.

Previously working ok (MSFS2020) but there was a recent Windows 11 update and a few MSFS updates.

Everything is set to start as admin.

The controls are shown and working in Windows.

Default MSFS control configs work ok.

None of my previously created profiles work at all.

Joy2key has stopped working too, and my Saitek pedals disappeared completely (I suspect because Windows update replaced the driver with one that didn't work with security options on).

My next steps are to remove and reinstall AAO but thought I’d ask here in case anyone else has similar issues.

14 minutes ago, NigeUK23 said:

My next steps are to remove and reinstall AAO

This will do nothing at all unless you delete the database and config directories too. \AppData\Local\LORBY_SI

14 minutes ago, NigeUK23 said:

but the app has completely stopped working for me

What exactly does that mean? Is the app not starting up, you don't get to the main screen, it is not connecting to the sim, the configs for the aircraft are not loading, all assignments are painted in red,  are there error messages - ??

 

Edited March 11, 20251 yr by Lorby_SI

2 minutes ago, Lorby_SI said:

This will do nothing at all unless you delete the database and config directories too. \AppData\Local\LORBY_SI

What exactly does that mean? Is the app not starting up, you don't get to the main screen, it is not connecting to the sim, the configs for the aircraft are not loading are there error messages - ??

 

Ok, this is what ‘not working’ means:
1. AAO starts with msfs (admin prompt comes up)
2. Previously created profile is loaded in aao and matches aircraft.
3. The inputs I previously configured have no effect in the sim. specifically, when I increase throttle using the hardware throttle, the throttle  does not change in the sim. If I move the mixture lever on the hardware, nothing happens in the sim.
No error messages.
If I close AAO and switch to an MSFS hardware profile then all the hardware controls work as expected.
MSFS is set to run as admin and AAO is too.

7 minutes ago, NigeUK23 said:

Ok, this is what ‘not working’ means:
1. AAO starts with msfs (admin prompt comes up)
2. Previously created profile is loaded in aao and matches aircraft.
3. The inputs I previously configured have no effect in the sim. specifically, when I increase throttle using the hardware throttle, the throttle  does not change in the sim. If I move the mixture lever on the hardware, nothing happens in the sim.
No error messages.
If I close AAO and switch to an MSFS hardware profile then all the hardware controls work as expected.
MSFS is set to run as admin and AAO is too.

When its loaded, are the assignments (axis and buttons on the main screen) in the config painted red? When Windows changes the ID of a controller, all assignments that were made with it will get a red background color.

What about when you create a new assignment, what happens there?

Edited March 11, 20251 yr by Lorby_SI

5 minutes ago, Lorby_SI said:

When its loaded, are the assignments (axis and buttons on the main screen) in the config painted red? 

No.

3 minutes ago, NigeUK23 said:

No.

Strange. Then there is no reason why they shouldn't work.

Check the AAO Blacklist. Go to "Hardware->Device Blacklist" and make sure that (only!) your flight controllers are in the list on the left. Everything else should be moved to the list on the right with the "Ignore" button.

Checked that.

I think the issue was that the 2 parts of the Velocity One got mixed up.

I noticed that when I turned the yoke, the throttle (in aao) moved and when I pushed or pulled the yoke, the propellor axis (in aao) moved.

I swapped them round (in hardware change) and it seems to be ok now.

Thanks for your replies.