Looking for some help to help out a newbie in stream deck and AAO.

 

I'm currently trying to create a replica of the Just Flight's F28 overhead panel on the stream deck.

I'm using the "receiving events from simulator" window to get the events and "observe Variables in simulator" to get the var's but there are a lot of switches that are not recognised or show in either window.

 

Now, will this be because of something from AAO, MSFS or Just Flight?

Most aircraft in MSFS use custom variables and events that the aircraft developer invented for his purposes. Mostly LVars, BVars and HVars. The lists in AAO on the other hand (can) only contain those assets, that are part of the official MSFS SDK. So you won't see any of those custom var anywhere in the app.

There are several strategies:

1. Go to flightsim dot to and look for AAO templates or StreamDeck profiles for this aircraft. These usually contain a script package for that plane that you can import into AAO (so this also makes sense if you don't even have a StreamDeck)

2. Use the MSFS developer mode. Open "Tools->Behaviors", then click back into the sim and hover your mouse over the switch you want to analyze. Press Ctrl&G and the behavior code of that switch will show up. Look through the layers of templates until you find the LVars, BVars etc. that operate this switch. Wrap those into an AAO script or add them to the AAO database (at the bottom of the Scripting menu)

3. If it is not a Marketplace aircraft, you can take a look into the behavior XML files of that aircraft and thread your way through the Templates in there.

4. If you know that an aircraft relies mostly on LVars, you can read those from the running sim with "Scripting->Read LVars from sim"

5. "Scripting->Read HVars and BVars from MSFS" is only of limited use these days. This feature analyzes the behavior files, but that doesn't work for Marketplace aircraft. Plus, MSFS relies on inheritance a lot, and most variable names don't even exist in readable form in the files. 

Edited July 22, 20232 yr by Lorby_SI

The F28 seems to use LVars are lot.

For example, this toggles the batt isolate 1 cover:
(L:F28_OH_Gaurd_3_Switch,·Number)·!·(>L:F28_OH_Gaurd_3_Switch,·Number)
(the typo is no accident, this is the actual name of the LVar)

and this toggles the switch itself
(L:F28_OH_BATT-ISO-1_Toggle_Switch,·Number)·!·(>L:F28_OH_BATT-ISO-1_Toggle_Switch,·Number)

Battery switch 1
(L:F28_OH_DC-BATT-BUS_Toggle_Switch,·Number)·!·(>L:F28_OH_DC-BATT-BUS_Toggle_Switch,·Number)

Battery switch 2/Ext Power
(L:F28_OH_DC-EXT-BUS_Toggle_Switch,·Number)·!·(>L:F28_OH_DC-EXT-BUS_Toggle_Switch,·Number)
 

On/Off scripts would be for example
0·(>L:F28_OH_DC-BATT-BUS_Toggle_Switch,·Number)
1·(>L:F28_OH_DC-BATT-BUS_Toggle_Switch,·Number)

So you can use option 4. Ideally together with 2, but the naming convention seems solid with this plane, so you could just filter for _OH_ on the variables list after you did the scan.

Edited July 22, 20232 yr by Lorby_SI