I have recently come to the conclusion that to operate the planes I enjoy flying in the way I want to, I will need to try out MSFS external programs to operate my peripherals. So here I am, dipping my toe into Axis and Ohs.

I have done a few weeks of research and I do believe I understand the basics of how and why things are the way they are but I have also reached my limit of understanding, even after watching or reading the resources regarding Axis and Ohs. In other words, I need help.

 

I would like to ask for help based on a simple example in the CJ4:

My intent is to use Axis and Ohs „on top of“ the standart MSFS keybinding profile. What I mean by that is I will program my Virpil Control Panel 3 with the basic stuff that can be programmed in MSFS and will use Axis and Ohs to configure it with the few things I need that can not be bound in MSFS. So for example, I will keybind the Parking Brake (example) to Button 1 (Example) in MSFS and then use Axis and Ohs to program the Gear Down (Example) to Button 2 (Example) wich i did not use in MSFS.

 

I assume this is possible ?

 

So I experimented around with one specific issue. I am trying to get the „Emergency Light Armed“ switch to work wich does not seem to be possible within MSFS. I started up AAO and figured that I should „Watch simulator events“.

So I did and once I weeded out all the other stuff that I wasnt looking for, I narrowed it down to these two events:

 

0 (>K:MASTER_CAUTION_SET)

1 (>K:MASTER_CAUTION_SET)

 

So then I moved on to „Add Button assignment“, figuring it would be a „key down event“. I was exited to see that there is already a whole list of events and even a filter function! But unfortunately, the events I found were not in this list.

 

No doubt I did something wrong or misunderstood something so now I am here, looking for help.

 

Any help, input and guidance would be much apprechiated.

 

Thank you in advance.

AAO has nothing whatsoever in common or to do with the MSFS controller assignments. They look similar in part but those are two completely different "logics". You can never assume that if something is there in MSFS it will be there with the same name or functionality in AAO.

AAO is basically just an interpreter between your external hardware and the MSFS SDK. And those lists in AAO are filled with what the SDK documentation yields as "official" variables and events. 

But.

The aircraft developers don't have to use any of those. Each assignment that you make for one aircraft may (will) be completely different for another plane. You can't rely on anything, especially not on those lists in AAO. And you can pretty much forget about "watching simulator events" and the other convenience methods. They show you the result of the button action, not the cause. OK? Buttons can be operated with K-Events, but in MSFS they rarely are. One has to look into the LVars, HVars and BVars in use for this particular aircraft. This involves activating the MSFS developer mode and looking through the Behavior code. Or go to flightsim.to and look for AAO templates or packages made for example for MIDI hardware or the StreamDeck. The hardware doesn't matter to you, what you want are the script files that come with them, that you can import into AAO and then assign to your buttons.

And that is where the RPN scripting comes in. You can try out the event above in the RPN editor (scripting menu) with the "Test" button (what you have there already is RPN code, value 1/0 is sent using the K event), to check if they really do what you think that they do (or if this event is just one result of the button being pressed, and a large part of its functionality would be missing if you only send that). Or, if you are certain about the name of a K-Event and it is really missing from the lists, you can add them to the AAO database manually (bottom of the Scripting menu).

That being said, the MASTER_CAUTION events are definitely there. Filter for "caution" and take a look into the "Aircraft Failures" group. I assume that you will have to send the "0" to switch off the master caution light (the little numerical box to the right of the key down event is for that purpose)

 

Edited June 15, 20232 yr by Lorby_SI

Thank you for your fast and extensive reply !

 

I see now that I did understand the basics mostly right but that I did not communicate very well. More importantly, I see now that I made one very stupid mistake: I thought when I watched the simulator events, those were some kind of LVARS variables. Yes ok, my mistake.

As for the rest, I guess I need to read up more and ask more questions as they come.

And the Master-Caution_Set was indeed there, I just missed it.

 

Again thank you.

 

 

Well, never mind. Looks like AAO has stopped recognising my peripherals. It worked before, now all I see is Keyboard, Mouse and Voice.

1 hour ago, Marcus Perry said:

Well, never mind. Looks like AAO has stopped recognising my peripherals. It worked before, now all I see is Keyboard, Mouse and Voice.

Are you looking at the "Device" dropdown? That is not how this works, you don't select your controller from there. Just move the axis or click the button. If AAO can see the controller, it will display it then and there.

Edited June 15, 20232 yr by Lorby_SI

19 hours ago, Lorby_SI said:

Are you looking at the "Device" dropdown? That is not how this works, you don't select your controller from there. Just move the axis or click the button. If AAO can see the controller, it will display it then and there.

Boy or boy, I am really doing it all wrong. Yes, I got it now. My bad... again.

 

Once again thank you for your help.