I put off buying any of the add on programs like LAAO because I felt they were beyond my capabilities to use. However, I finally bought LAAO, primarily to map switches on my Alpha and Bravo that I could not do with the in-sim mappings...and for that it's just perfect and I can do it. Now, however I have something I want to do that goes well beyond the previous. I want to be able to use my Alpha magneto switch, individually on each engine on a two or four engine propliner. I don't fly jets, just GA and the classic propliners (D-18, DC-3, DC-6 & L1049). On most of these it's a real trick to do the mag drop test using the mouse to flip a switch (or turn a knob) and then move the eyepoint to the RPM gauges and then back to the switch/knob. So, I thought if I could map the rotary switch on the Alpha to each engine individually, I would never have to take my eye off the RPM gauges. Well, I've been trying to do this for the last month and about the only thing I've accomplished is getting headaches. I've gone over the manual several times, watched the SimPit Foundry video's (he even gave me some hints...which I didn't understand) but not even close to understanding how to make this happen. I hate to use this excuse...but I think this old dog is just not able to learn new tricks. I really have no desire to learn scripts and the more advanced stuff that LAAO can do.

So, I'm asking if anyone has done this on any of these aircraft would you please share your secret with me. If no one has, I would be willing to pay for someone to do it for me.

Thanks for any help anyone can give.

Garry

The actual implementation will probably be different for every single aircraft. AxisAndOhs is essentially just a translator between you and the MSFS SDK. The variables and events that you see in the AAO lists are those from the official MSFS SDKs. Unfortunately, aircraft developers don't care much about these standards, and they implement their control schemes whichever way they want (IEs, BVars, LVars, whole scripts). In some cases, there isn't a way to move a switch in the cockpit at all, because they only implemented mouse controls.

Personally, if you need individual controls, I would use AAOs control layer logic for that

1. Figure out if the engine/magneto controls can be actuated remotely - like, at all

2. Then figure out how to do what you need for a single engine, create the necessary button assignments

3. Copy, paste and edit these assignments for the second engine, and move them on the yellow control layer

4. Repeat for the third engine, put those on the red layer

5. Repeat for the fourth engine, put them on the green layer

6. Assign the event "AAO_CONTROL_LAYER_TOGGLE" to a button - each click will switch to the next layer and give you control over that specific engine.

I can create a template for one of your aircraft, but I will need the exact name, model and developer for it, and a detailed description of what operation you are doing with the mouse that you want to implement in AAO. Be mindful that I don't have an Alpha, I can only do this with the rotary selector on the Bravo - hoping that it works the same way (=each position corresponds to a joystick button press)

Edited July 14Jul 14 by Lorby_SI

Thanks for the quick response. I am out of town until next week so let me get back to you then with a more complete response.

Thanks again.

Garry

On 7/14/2026 at 5:14 AM, Lorby_SI said:

The actual implementation will probably be different for every single aircraft. AxisAndOhs is essentially just a translator between you and the MSFS SDK. The variables and events that you see in the AAO lists are those from the official MSFS SDKs. Unfortunately, aircraft developers don't care much about these standards, and they implement their control schemes whichever way they want (IEs, BVars, LVars, whole scripts). In some cases, there isn't a way to move a switch in the cockpit at all, because they only implemented mouse controls. My responses are in Red below...and thank you very much.

Personally, if you need individual controls, I would use AAOs control layer logic for that

1. Figure out if the engine/magneto controls can be actuated remotely - like, at all. The engine magnetos can be controlled from my Alpha using the Magneto Switch. The problem is using the native sim commands (Magnetos Both or Left or Right) it does all engines at once...or if I pick any single engine, it will only switch the magneto for that engine.

2. Then figure out how to do what you need for a single engine, create the necessary button assignments

3. Copy, paste and edit these assignments for the second engine, and move them on the yellow control layer

4. Repeat for the third engine, put those on the red layer

5. Repeat for the fourth engine, put them on the green layer

6. Assign the event "AAO_CONTROL_LAYER_TOGGLE" to a button - each click will switch to the next layer and give you control over that specific engine. This would be perfect.

I can create a template for one of your aircraft, but I will need the exact name, model and developer for it, (The aircraft would be the Microsoft/Aeroplane Heaven Douglas DC-3 Pax Classic and the PMDG Douglas DC-6B) and a detailed description of what operation you are doing with the mouse (not using mouse...using the Magneto Switch on the Alpha (see photo attached) and just turning the switch to Left or Right or Both or Off or Start) that you want to implement in AAO. Be mindful that I don't have an Alpha, I can only do this with the rotary selector on the Bravo - hoping that it works the same way (=each position corresponds to a joystick button press)

15 hours ago, flytriman said:

The engine magnetos can be controlled from my Alpha using the Magneto Switch. The problem is using the native sim commands (Magnetos Both or Left or Right) it does all engines at once...or if I pick any single engine, it will only switch the magneto for that engine.

When you already know how to target each individual magneto, I suggest that you follow my instructions above. Create the appropriate assignments for each engine, then move them to other control layers. One layer for each engine, with a button to switch between the layers.

Edited 23 hours ago23 hr by Lorby_SI

15 hours ago, flytriman said:

(not using mouse

That is not what I meant. Most aircraft don't use the default SDK events at all for cockpit interaction (but they might use them inside their own code). In this case, in order to assign stuff in AAO, you have to analyze the behavior code = what exactly is happening inside the aircraft/simulator "under the hood" when you operate the switch/knob/lever/whatever with the mouse. Then replicate this code in AAO. The mouse is the preferred/official control method, that is why one has to take this route.

The standard way to do that is to activate the MSFS developer mode, open Tools->Behaviors, then click back into the sim, hover the mouse over the knob/lever/etc. in question and press Ctrl+G. That will in most cases load the behavior code, and you can look at the ...Interaction... or ...MouseRect... components to figure out what you need to do in AAO.

If the aircraft is reacting to the default event, fine, you're good. If the aircraft developer provided MSFS IEs, even better. If there is neither option, behavior code is the way to go.

Edited 22 hours ago22 hr by Lorby_SI

15 hours ago, flytriman said:

PMDG Douglas DC-6B

That one is the perfect example of what I was talking about. You can control all 4 switches at the same time with the "global" SDK events (MAGNETO_OFF, MAGNETO_RIGHT etc.). But you cannot control them with the individual events (MAGNETO1_OFF, MAGNETO1_RIGHT etc.). Some weirdness in the aircraft code interferes with the individual events and makes them move the knob to incorrect positions.

Apparently, for this aircraft, individual scripts are required to achieve individual control.

Here is a template that does this - bear in mind that it was made for the Bravo Throttle, you will have to reassign all positions of the rotary encoder and the button that switches the layers.

PMDG_DC6_MAGS.zip

Edited 20 hours ago20 hr by Lorby_SI

Ah OK, now I get it. The mag events are all on/off toggles. That's why they behave like they do. I've updated the template, it should work for all planes that use the default mag events.

Thanks...I'll give all this a try and let you know. I did know about using the Ctrl + G to find the command...I just did not know how to assign a single engine.

Garry