Hello again Folks.

Can anyone help me out with this question please? I am trying to display the appropriate blank button and starter engaged hatched icon from the Citation Longitude icon pack by Guenseli. The blank button is the icon for the starter when it is disengaged and the hatched square icon is used when it is engaged. 

I'm using a MultiGauge from Lorbys plugin for my SD+unit and I'm using an A variable in the Visibilty section with this code line  GENERAL ENG STARTER:index, Bool    I'm not very familiar with this, so do I need to amend this in some way for the sim to recognise it? I have three image definitions, two for the blank button and one for the hatched square when the starter is engaged. I'm using a 0 for the Visibilty Value of the blank button and a 1 for the Visibilty Value of the hatched square. I'm using this K SET_STARTER1_HELD for the Key Event with 1 and 0 for the down and up actions.

The starter is working in the sim when I press my SD+ button, but the icons are not displaying in my SD+ button. That's why I'm thinking I need to amend my A variable, but I don't know what change to make to the code line.

Thanks...Kenny.

 

 

 

I've never used a streamdeck, but the A variable with the index, you'll need to replace that with a number for example (A:GENERAL ENG STARTER:1, bool) for engine 1. Sometimes they count from 0 so that may be engine 1. 

8 hours ago, kenny584 said:

Hello again Folks.

Can anyone help me out with this question please? I am trying to display the appropriate blank button and starter engaged hatched icon from the Citation Longitude icon pack by Guenseli. The blank button is the icon for the starter when it is disengaged and the hatched square icon is used when it is engaged. 

I'm using a MultiGauge from Lorbys plugin for my SD+unit and I'm using an A variable in the Visibilty section with this code line  GENERAL ENG STARTER:index, Bool    I'm not very familiar with this, so do I need to amend this in some way for the sim to recognise it? I have three image definitions, two for the blank button and one for the hatched square when the starter is engaged. I'm using a 0 for the Visibilty Value of the blank button and a 1 for the Visibilty Value of the hatched square. I'm using this K SET_STARTER1_HELD for the Key Event with 1 and 0 for the down and up actions.

The starter is working in the sim when I press my SD+ button, but the icons are not displaying in my SD+ button. That's why I'm thinking I need to amend my A variable, but I don't know what change to make to the code line.

Thanks...Kenny.

 

 

 

Using MSFS devel mode to look at the behavior code (=this is how the button itself does it when you operate it with the mouse)

Button down: (>B:ENGINE_Starter_1_Push)
Button up: (>B:ENGINE_Starter_1_Release)

Read Engine Starter state: (A:GENERAL ENG STARTER:1, Bool)

Edit: instead of the BVars you can of course also use the InputEvent (IE:) that they are the bindings of. IEs can be picked directly from the event list in AAO once you are connected to the sim and sitting in the cockpit, as they are read from each aircraft at runtime.

The strategy with unknown aircraft logic should always be this:

1. check MSFS InputEvents first. Use the "Filter" box on the event selection dialog to find them (for example, type "starter" and press Enter). 

2. When the IE doesn't work out of the box, use its bindings instead, the BVars. They have the same name with a "do-word" at the end (_Set, _Toggle, _Push, _Release etc.). 

3. Try reading the state of the switch off the IE or the BVar. Only if that doesn't work resort to other variables, like AVars. And if that fails too, make AAO read all LVars from the sim (menu "Scripting" and check those out, see if you can find the LVar that is responsible for the animation or emissive properties (=a lit LED or something).

Personally, I prefer to look at the behavior code directly. It may take some rummaging around, but at least I know that I am looking at the correct component. In AAO I then use the Script Editor to try them out and the Variable Watcher to see the result.

 

Edited July 5, 2025Jul 5 by Lorby_SI

Hello again, and many thanks for your detailed explanation. It's those details that I am unsure of. I must also offer my apologies to you, because I remember you pointing me to the devel mode way of finding out things a while back. I forgot about using it. I don't often get a chance to do this, as I have to care for my wife more and more these days. I do enjoy working with my SD+ and Xtouch mini with AAO and fs2020. It keeps my mind active, even though I don't get much time to actually fly the aircraft...LOL.

I'll try to do more detective work before asking questions of you, but sometimes I get lost between all the variables!!

Best Regards...Kenny.

41 minutes ago, kenny584 said:

sometimes I get lost between all the variables

Nobody can really know them - the aircraft developers are just inventing them as required. With the MSFS sims you can consider yourself lucky when one of the official SDK events or variables actually work in this context.

44 minutes ago, kenny584 said:

do more detective work

Until you feel comfortable with deconstructing behavior code, asking here is the better option.

45 minutes ago, kenny584 said:

have to care for my wife more and more

Sorry to hear that. Best wishes!