Hello, unfortunately AAO no longer recognizes my hardware when assigning buttons. However, all devices are listed under hardware. What can I do? I’m back to version AAO-2-09-b04. Here I can enter again, but unfortunately only cumbersome because AAo takes the last key assignment out of me. Please help. Thanks very much. Sorry for my poor english. “Google”
Spandau.
@ Fioretto1961
I’m not sure that I understand. Please send an email with your proof of purchase (order number and shop) to the address on the last page of the AAO manual. Include a detailed description of what you are doing and what hardware is involved.
Hello @ll,
for those of you who like to tinker I’ve uploaded a small HTML sample page to the AAO website, that uses the AAO WebAPI to generate a (very) simple moving map based on Leaflet, which is in turn using OpenStreetMap. All that is required for an app like this is half a page of Javascript (and it can probably be done a lot better, this is just an example!).
1 Like
Hello,
Would it be possible to share the script and template for the A32NX with me? I tried what I found on the internet, but it doesn’t work well.
If you also have one for the Caranedo M20 … Thank you all.
Did you contact the author of the template? I imagine that he would like to know when his creation doesn’t work. He might also be able to help you to get it working in the first place.
1 Like
Really appreciate all the work you do with the program and providing support.
I am having a interesting issue that I have been troubleshooting for a few days.
Lately, when using AAO with my hardware in MSFS, I begin pressing buttons on my controllers setting up for flight, and after a while suddenly neither controller button presses or mouse clicks on the VC operate correctly.
I have quite a few controllers, including a Logitech switch panel, 5 Go-Flight modules, 2 Thrustmaster F16 MFDs, an X-Touch mini, TCA sidestick and TCA throttle and add-on.
Thanks to AAO and your support, I can almost completely fly the FBW A320neo Dev. version with minimal mouse clicks normally.
However, lately I have been having this issue and have to resort to restarting the sim and flying without AAO running using only VC mouse clicks.
Any idea what might be going on? I do start AAO before starting the sim and run everything as an administrator.
Really miss using AAO to fly. I am not sure what I am doing wrong.
Any help or suggestions appreciated!
What kind of issues exactly? What does “don’t operate correctly” mean?
Can’t say that I’ve heard this before.
Only things that come to mind are
- cross-compatibility issues (=interference from another addon, particularly other controller plugins or apps)
- Event flooding because you have a script running somewhere that changes stuff every few milliseconds back and forth all the time or a stuck button/axis that forces the plane to do “something” continuously.
- Range problems when setting LVars (= setting LVars to negative values that cannot be negative, that kind of thing. Happens a lot with hand-made INC/DEC scripts that don’t bother with range protection code)
- issues inside the aircraft programming logic itself (= in the sim).
Mind you, these are just thoughts. I have no idea whatsoever about what is actually happening.
Are you sure that this isn’t a general instability in the FBW development version? After all, that isn’t a stable release version, right? Did you ask FBW? If mouse operated controls inside the VC break, they should be able to tell you why.
Appreciate your thoughts.
I’m guessing it’s a controller related issue since the FBW dev version works well when using the VC mouse clicks with just the TCA sidestick and throttle.
Will try disconnecting the various controllers and reconnecting one at a time to see If I can isolate a culprit.
Thanks again.
Or try and create a new configuration from scratch, maybe with a different livery of the plane. Add things one by one until it starts to go wrong.
Yes I did but no answer. Even with my own templates, I have problems with the functions on the plane. I will continue my research …
You will have to be a lot more specific if you want help with that. What functions exactly(!) and what kind of problems?
When I fly with the A32NX, the NAV Mode button does not turn, Range, does not turn, Speed does not work, HDG does not work, altitude is OK. And that’s how it is with almost all functions. COM works …
I managed to get a Template to work on the M20R tonight, but the A32NX dev or Exp nothing to do.
It’s not easy with google trad… I’m sorry…
If you downloaded template from flightsim.to, it seems to be pretty old. A lot of variables have changed since then.
When I’m on my PC next time I can post my template for a32nx which works.
1 Like
Here’s template for FBW A32nx experimental version. Printable overlay included in the zip.
https://github.com/blindye/aao_guides/releases/download/fbw_a32nx_exp/FBW_a32nx_exp_xtouchmini.zip
Installation:
- Extract .tmpl file from the zip.
- Load up the FBW in airport
- in AAO Templates → Import template → Choose extracted .tmpl file
- Templates → Apply template to this aircraft → Choose FBW_a32nx_exp_xtouchmini
For rotaries Baro and COM works in both layers. A layer functions are above and B layer below for other rotaries (for example NAV MODE is working in A layer and PFD brightness in B layer).
Below rotaries S: SEL means Short press of the rotary is Selected mode, L: MAN means Long press of the rotary is Managed mode.
For buttons text above button is Layer A and text below button is Layer B.
For example first button on top row: Layer A = FD, Layer B = ADIRS 1 knob.
Button below that: Layer A = Taxi lights switch, Layer B = APU Master
Light switches:
Taxi lights switch turns on/off Nose light and RWY Turn lights
Strobes: Off → Auto → Off
LDG Lights: If led is off, first push unrectars landing lights, next push turn on (also turns on TO taxi light) → turn off → turn on etc. When ldg lights are turned off, long push of the button will retract the lights.
Long pressing Cabin call button is T/O Config button, not mentioned in overlay.
Most of the stuff needed before aircraft is moving are in Layer B, and after all preparations are done and you are ready to taxi only Layer A is needed.
All button LEDs should be working correctly.
1 Like
Regarding the not working template for the A32NX:
I updated the template on flightsim.to a few days ago after testing it on 2 different setups where it performed well with su5 and the then latest AAO release and dev-version of FBW.
I also answered on flightsim.to, but since I‘m on vacation in a different timezone and spending half of my day without internet-coverage it may take longer than a few hours to answer…
Maybe you have more luck with the template from bLindyee and the ’bus will hopefully be your friend again. 
Thank you both very much for your answers.
@bLindyee I will try your template out tonight and I will come back here to tell you what it is. @Axisor0 you did a great job with your template and the concern must come from me and not from your Template. Thanks to you two.
The profile works very very well thank you very much to you.
I have for example the ADIRS which does not turn when I press but the LEDs work very well or the landings light or only one retracts. But these are just details. Thank you very much.
I also tried the @Axisor0 profile which also works now apart from a few functions … I don’t understand anything anymore, but thanks to you, I can finally enjoy my X touch and AAO 
Is there a way to have custom Views depending an the aircraft?
Right now you save the Custom Views in MSFS. So you have to make a Controller Profile for every plane.
As AAO regognices the aircraft it would be nice to have custom views depending on the aircraft. And in the next step load a custom Profile onto stream deck to access the views.
But aren’t the custom views aircraft specific? I thought that the controller profile only handles calling them, not their content itself?
Generally speaking, this is a different app (CameraPositionX) which we would love to make compatible. Unfortunately most of the camera controls in SimConnect are non-functional. In fact, in the latest versions of the SDK, the SimConnect native camera controls have disappeared entirely from the documentation.
Guess i have to check that
Hi folks, 3 questions:
- Recently I asked if it is possible to use two Stream Decks at a time with AaO. I found out the hard way, just using them actually is. Editing them is a problem. I had lots of CTDs, first the SD app is gone, then the sim crashes right afterwards. AaO window remains, but I am losing all my scripting progress of the current session. Is there any way AoO could keep the recently generated or updated scripts, perhaps with a future AaO update?
- I am new to RPN scripting. For my favorite aircraft, the Longitude, I couldn’t find much. So I downloaded lots of stuff I couldn’t use, just to check on how it’s to be done. Now I am getting better and all those downloaded scripts have lost their use. Is there a way to delete installed scripts on the bulk, like folder-wise? The only way I can see is one by one, but there are hundreds of them.
- I am using a Saitek FIP in PFD mode. When I started using AaO I deleted the Saitek plug-in, kept the driver, as stated in the manual. I noticed that now the Mach speed display and the Baro setting (QNH) now don’t show decimal values other than zero. Is there any way to fix that?