Hi. I am trying to assign the display change buttons in the CJS Typhoon via AOO to Streamdeck buttons. I have found the variables which change when I click the buttons in the cabin but when I assign them via script, to a Streamdeck button or just hit the test button in AOO, only the MFD buttons change, not the actual screen graphics. I cannot for the life of me find an event other than observing the values of the LVars change when I press the button in the cabin. The script I have tried is as follows, it is for the left hand configuration button ie map on MFD1, Engines on MFD2:

8 (>L:EF2000_MHDD_CURRENT_PAGE:1, Number) 1 (>L:EF2000_MHDD_CURRENT_PAGE:2, Number)
 

This is the last function set I need to almost remove the need completely for mouse use during flight. Can anybody guide me in the right direction please... keeping in mind I am very green-coloured where this stuff is concerned. Many thanks in advance.

 

Glynnski

5 hours ago, Glynnski said:

Hi. I am trying to assign the display change buttons in the CJS Typhoon via AOO to Streamdeck buttons. I have found the variables which change when I click the buttons in the cabin but when I assign them via script, to a Streamdeck button or just hit the test button in AOO, only the MFD buttons change, not the actual screen graphics. I cannot for the life of me find an event other than observing the values of the LVars change when I press the button in the cabin. The script I have tried is as follows, it is for the left hand configuration button ie map on MFD1, Engines on MFD2:

8 (>L:EF2000_MHDD_CURRENT_PAGE:1, Number) 1 (>L:EF2000_MHDD_CURRENT_PAGE:2, Number)
 

This is the last function set I need to almost remove the need completely for mouse use during flight. Can anybody guide me in the right direction please... keeping in mind I am very green-coloured where this stuff is concerned. Many thanks in advance.

 

Glynnski

LVars are normally used to control the animations and emissive properties of something. They are not "input events" of any kind. Yes, some aircraft developers use them for that too, but that is their choice, and not how it is specced. Animation and actuation of the aircraft system bound to this button are two separate things that more often than not can be controlled and triggered separately from each other.

I recommend analyzing the buttons in the MSFS developer mode: devel mode on - open "Tools->Behaviors", then click back into the sim, hover the mouse over the button/lever/knob that you are interested in, and press "Ctrl - G". This usually brings up the behavior code, and you can check out the "...Interaction..." and "...MouseRect..." components for the actual code that is called when you operate it with the mouse. That is what you want to replicate in AAO. 
Be mindful that there are controls that can only be operated with the mouse (because the developer made them so). There is nothing you can do when there are only O: or I: variables in the behavior code, they can't be accessed from the outside. 

Edit: specifically with MSFS2024 you should be checking out the MSFS Input Events first though. They are on a separate tab in AAO, but they only show up when you are sitting in the cockpit (they are unique for each aircraft and AAO reads them from the sim once you are in the cockpit).

Edited December 14, 20241 yr by Lorby_SI

Fantastic thanks very much for the info. As a complete newcomer to this kind of thing (although I do primitive coding in C# from time to time) could you recommend any resources where I can learn how it's all done? I know about the SDK spec but it's all a bit overwhelming for a simple bloke like myself :)

44 minutes ago, Glynnski said:

Fantastic thanks very much for the info. As a complete newcomer to this kind of thing (although I do primitive coding in C# from time to time) could you recommend any resources where I can learn how it's all done? I know about the SDK spec but it's all a bit overwhelming for a simple bloke like myself 🙂

The problem is that most aircraft developers don't care about the specs and how it is all done, they all follow their own logic. As a user (I count myself among those too), you never know what you are going to get with a new aircraft model. That has been an unfortunate development from the start of MSFS. Probably because there was no SDK everybody started to work around it in their own way. 

This is really more detective work than something one can learn or study.

Is that Typhoon a payware or freeware plane? Where would I go looking for it?

Edited December 14, 20241 yr by Lorby_SI

Ok, so I bought the plane. 

I'm not exactly sure which buttons you mean, so I am assuming we are talking about the 17 square buttons around each MFD. Correct?

These are all controlled by Input Events and you will find them on the AAO event selection treelist in the tab "MSFS IEs" (assuming that you have the latest version of AAO)

If you want to call them from the StreamDeck, use the Type "IE:" for Key Down and then enter the name of the input event into the box. You can type it in, or copy it from the Event selection treelist (left click-right click) and paste it into the box with Ctrl-V.

If you want to enter them manually, the syntax goes like this:

AS04F_DDI_Push_1_MFD_1

The first "1" is the index of the button, the last "1" is the index of the MFD. In this example we would trigger the top left button on the left hand MFD. Buttons are numbered 1-17 counterclockwise, starting top left, MFDs are 1 left - 2 right and the lower one is 3

AS04F_DDI_Push_7_MFD_3

Pushes the bottom left button of the lower MFD.

Etc.

 

 

 

Edited December 14, 20241 yr by Lorby_SI

Thanks so much for taking the time out your replies have been invaluable already. The buttons are at the bottom of the pedestal for the vid changer but I used your info (Ctrl +G) to get the info I needed for the 'click events'. Not having as much luck with the ALT and Speed selectors or the up and down buttons, on the Autopilot panel... I like a challenge though, many thanks again and sorry I made you buy the plane! 🙂

13 minutes ago, Glynnski said:

I used your info (Ctrl +G) to get the info I needed for the 'click events'.

When you look at the Behavior Code, check the mouse components first. They are usually called something with "...Interaction..."

If there is a BVar in there you can use that too, but BVars and IEs are related, and you will probably find an IE in AAO with the same name that does the same thing.

 

Superb, this is the kind of info I need... thanks so much again! 🙂

7 minutes ago, Glynnski said:

Superb, this is the kind of info I need... thanks so much again! 🙂

I some cases you may have to replicate entire scripts. Disregard I: and O: variables, those don't work. And be mindful that simulator LVars require a Unit in AAO. When in doubt use the default ".Number": (L:somename, Number)