After losing random bindings after updating to SU2, I would like to use AAO for everything moving forwards.

1. I know how to save and link a master template but I haven't figured out how to edit the assignments, or add more, if I am in a different livery/aircraft to the one that the master template was created in. Is this possible?

2. If I create a general set of controls e.g.throttle axis, gear up/dn etc, how can I use this as a baseline and then add custom controls for specific aircraft e.g. Condition Lever for Turboprops?

3. What I am struggling with is how to create, save and then apply a master template over multiple liveries without having to select it for each livery. And then add custom controls on top of the master template.

Thank you

In the Templates menu there is the option "Link a Template to this aircraft". On that dialog you can link any number of templates to an aircraft. So you can create several partial templates and link them, then add the custom controls on top.

If you have to edit templates, there are several ways. I usually do this in Offline Mode, where I can choose to load either a configuration or a template on the main AAO dialog. Other testers are doing this "live", they have a base configuration for a specific aircraft, edit there and then save the config as a template again, overwriting the existing one. All aircraft configs that link this template then have the new controls.

About the teminology: there are no "profiles" in AAO. The Axis and Buttons and Scripts that are assigned to an aircraft (livery) are called "Configuration". They are the "live" part. Separate from those there are the "Templates", which essentially are just blueprints for Configurations. When you "Apply" a template, AAO clones the contents of that template into the currently active config (=the controls are all local to the config, changing the template does not change the config, they are not related anymore). On the other hand, when you "Link" a template, the config and the template are associated with one another. Any change to the template will affect the config.

Edited May 19, 20251 yr by Lorby_SI

As always, I appreciate your help understanding how to better use AAO, thank you.

 

Lorby, I have tried looking for 'Translate Cockpit View Backward' in AAO's input menu but there's nothing there.
How do I populate the menu with default MSFS actions like this one, if I want to rebind default keybinds?

 

Edited May 20, 20251 yr by toby23

27 minutes ago, toby23 said:

Lorby, I have tried looking for 'Translate Cockpit View Backward' in AAO's input menu but there's nothing there.
How do I populate the menu with default MSFS actions like this one, if I want to rebind default keybinds?

 

The events in AAO are the ones from the MSFS SDK. They are not related and they have nothing to do with those in the MSFS controller assignments. Those are two completely separate logics that don't overlap. Some items may have similar names, but they are not the same. What AAO is allowed to do over SimConnect has nothing whatsoever in common with the MSFS controller assignments.

Sorry to say, but the camera events are non functional in the SDK, they have been since the Alpha of MSFS. Not sure why, but Asobo never fixed them. So a direct assignment of camera pan/movement controls is impossible. Most people use virtual events for this when they want to trigger then trough scripts (= virtual keyboard events, vJoy or VIGEm)

With AAO you can only access the camera variables (see MSFS SDK documentation Camera Variables ), but that is tricky business. On flightsim.to there are some StreamDeck profiles that have a collection of camera related scripts, those usually work (=change to a specific cockpit/outside/drone camera position).

And/or petition Asobo that t hey finally fix the camera events that are even listed in their own SDK documentation. I've given up on those events.

Edited May 20, 20251 yr by Lorby_SI

11 minutes ago, Lorby_SI said:

The events in AAO are the ones from the MSFS SDK. They are not related and they have nothing to do with those in the MSFS controller assignments. Those are two completely separate logics that don't overlap. Some items may have similar names, but they are not the same. What AAO is allowed to do over SimConnect has nothing whatsoever in common with the MSFS controller assignments.

Ok, thanks for clarifying that. Looks like I will have to use MSFS for some commands then. At least the 'General' keybinds don't seem to disappear like the 'Aircraft' ones do. Thank you