Good Evening All, 

I have now took on what seems to be a mammoth task of setting up the A320, after getting used to BVars in the Asobo 152 and 172 i thought "it maybe time consuming but how hard can it be" 🙂 that was a mistake haha. 

I have had a look at "watch sim events" and a lot don't come up at all so i thought ill jump into developer mode and try looking for the BVars in behaviours, a good many of them work as expected when doing the previous profiles but a huge amount dont seem to so i took to flightsim.to to download a profile and have a look see how others have done it. I then got inspired to have a go but ended up rather confused. (I am still very new so not hard 🙂) 

I took a look at some of the scripts for simple button presses for example

(L:INI_APU_BLEED_BUTTON, number) ! (>L:INI_APU_BLEED_BUTTON, number) (L:__APU_BLEEDIsPressed, number) ! (>L:__APU_BLEEDIsPressed, number) 

This pushes the APU Bleed as expected so i thought id try and find the information through developer mode to do a button that isnt mapped on the profile i was looking at so i started right at the top - Blue Pump Ovrd Guard 

Opened behaviours and hit CTRL+G to have a look and found the following in Mouse reacts 

                
                            (L:__SVC_BLUE_PUMP_OVRD_GUARD_State) ! (>L:__SVC_BLUE_PUMP_OVRD_GUARD_State)
                            (L:__SVC_BLUE_PUMP_OVRD_GUARDIsPressed) ! (>L:__SVC_BLUE_PUMP_OVRD_GUARDIsPressed)
                        
            

I thought this looks similar i will give it a go... but when copy and pasting to use as a S: on a toggle button - Nothing happens 

Would someone be able to talk me through extracting the information i need from this/the sim and how to turn it into a workable function - hopefully if im talked through 1 function i maybe able to make a lot of progress with other buttons using the same technique?

Thanks as always - this is a great community to be a part of and the help is amazing. 

12 minutes ago, Sanguinus0014 said:

how to turn it into a workable function

Your LVars are missing the "Unit". See AAO manual, chapter about scripting. When you want LVars to be transmitted to/read from the simulator, you MUST add a Unit. Otherwise the LVar is treated as an internal one and will never leave the AAO app. This has been made so you can create your own variables in your scripts, for whatever purposes you need (counter, index, maths, whatever), without weighing down the interface to the sim with useless information.

So theoretically this: (I'd suggest testing them in the AAO script editor first...much less cumbersome)

(L:__SVC_BLUE_PUMP_OVRD_GUARD_State, Number) ! (>L:__SVC_BLUE_PUMP_OVRD_GUARD_State, Number) (L:__SVC_BLUE_PUMP_OVRD_GUARDIsPressed, Number) ! (>L:__SVC_BLUE_PUMP_OVRD_GUARDIsPressed, Number)

Can't test it at the moment though.

1 hour ago, Lorby_SI said:

Your LVars are missing the "Unit". See AAO manual, chapter about scripting. When you want LVars to be transmitted to/read from the simulator, you MUST add a Unit. Otherwise the LVar is treated as an internal one and will never leave the AAO app. This has been made so you can create your own variables in your scripts, for whatever purposes you need (counter, index, maths, whatever), without weighing down the interface to the sim with useless information.

So theoretically this: (I'd suggest testing them in the AAO script editor first...much less cumbersome)

(L:__SVC_BLUE_PUMP_OVRD_GUARD_State, Number) ! (>L:__SVC_BLUE_PUMP_OVRD_GUARD_State, Number) (L:__SVC_BLUE_PUMP_OVRD_GUARDIsPressed, Number) ! (>L:__SVC_BLUE_PUMP_OVRD_GUARDIsPressed, Number)

Can't test it at the moment though.

This has worked perfect thank you. 

This should hopefully be the last question on this... how would i go about finding/writing a variable to read this back so the button on the streamdeck displays correctly even if i accidently press something in the sim not on the device? 

There is no clear answer to that. I would look at the materials, the animations and the emissive properties of the switches' behavior code.

Looking at the code above, I'd suggest the first of the two LVars. The name and the way that it's used suggests that it holds the state of the switch or the aircraft system behind it.

OK thank you for the advice I will have a look 🙂