Don’t beat yourself up too much, same thing happened to me once too… 
Thanks to your advise I started to fiddle with the layout of my Saitek FIP. This is so cool that technically with AaO it is possible to create your own FIP design. Most of the things I tried worked fine. But there is this one thing that makes me scratching my head. I threw out the Speed Bug and the Altimeter Bug and replaced them with displays of the respective AP HOLD VAR. Of course I mostly copied the code of the respective INDICATED value, just altered the variable and the y-position value. But I also replaced the background mask. I just created a simple file in MS Paint with a 1 pixel cyan frame and a black background. Now, while the original background actually has a black background, the FIP shows the cyan frame of my newly created mask, but keeps the black background see-through. I was wondering if you could point out, what does it take for a background mask to be displayed or to be see-through?
Edit: Sorry I neglected to mention I am talking about the PFD display.
IIRC pure black (0,0,0) is seen as transparent by the FIP logic. Try something slightly not-black (1,1,1 etc.)
Hi Oliver,
Great program all around. I was wondering if it would be possible, when you press a switch/button in the cockpit, to have the feedback in the Lorby UI, like the corresponding script or variable would get highlighted. Sorry if it’s a naïve question, that would help me put the correct variables in my StreamDeck. Thank you!
That worked! Thank you so much!
Similar question, different hardware: Could you please also point out how to get transparent parts in the layers of the Steam Gauge and Slider Gauge of the Stream Deck plug-in? The same way?
I would like to see this too and I believe that SPAD.NEXT does this but I think it’s been asked before and it was determined that for whatever reason it could not be done in AAO. I could be mistaken though as I often am.
Use PNGs with transparency.
Because it would not work sufficiently well.
- HVars and Bvars cannot be tracked at all
- LVars can only be tracked if you know their names in advance
- AAO could track the ~2000 default simulator events and variables, but in most cases triggering them is not enough to operate the switch in the cockpit.
- The MSFS developer mode, Model behavior debug already reveals all required code.
- The BVar input events that have been introduced in SU5 are being used all over now. They cannot be read nor operated from the outside anyway. We are hoping that Asobo makes them accessible at some point.
So from my point of view, this would be a lot of work to create something that cannot work right - and that the sim itself does better anyway.
Hello @ll,
AxisAndOhs version 2.21 will have the ability to operate BVar controlled input events in MSFS. If you are being held back by the BVar logic too, and are a user of AAO with a bit of experience in RPN scripting, you are welcome to try it and maybe help finalizing the procedure so everybody can use it. Just send a message or email with your proof of purchase to the address on the last page of the AAO manual.
2 Likes
Can anyone help me make a script to use a Warthogs speedbrake thumbswitch to control spoilers/speedbrakes in game?
The switch is momentary (Backward - Neutral - Forward) and the intended functionality would be to have it incrementally open/close the spoiler axis…is this possible?
Did you try reading the spoiler handle variable, incrementing/decrementing it and writing the result back to the sim?
But that may be aircraft specific, so you may need different scripts for different aircraft. What plane do you want to use this with?
Mainly the FBW 320NX and the CRJ…i know both would probably require separate scripts. I read the docs but not sure how to script it out unfortunately.
I thought it might be something that would utlitze SPOILERS_SET, but I am deficient in figuring out how to make that work for my usecase.
I am having issues with the update of variables on a Stream Deck. I use two of these, one is mostly for inputs (key events) and didn’t cause any problems yet. The other is for display of state variables. This is of course a work under construction, getting bigger and more complex day by day. And now I notice on each and every flight that not all variables getting updated. Sometimes it happens right from the start, sometimes it happens mid-flight. On the vast majority of occasions it happens to String variables, but not exclusively. When it happens, most of the time the variable values just freeze, but on some rare occasions they also show implausible values. The display usually can be fixed by switching to another SD profile and then back to the MSFS profile. I was wondering if there is a better way to fix this or even to prevent this from happening?
Probably something like this for default planes and the FBW. Not sure though, this is off the top of my head
INC
(A:SPOILERS HANDLE POSITION, Number) 1.0 < if{ (A:SPOILERS HANDLE POSITION, Number) 0.1 + } els{ 1.0 } 32767 * -16384 + (>K:AXIS_SPOILER_SET)
DEC
(A:SPOILERS HANDLE POSITION, Number) 0.0 > if{ (A:SPOILERS HANDLE POSITION, Number) 0.1 - } els{ 0.0 } 32767 * -16384 + (>K:AXIS_SPOILER_SET)
Hey LorbySI, I’m trying to change the lights on the Bravo throttle for the FBW A320. For example the Autopilot LED needs to be set when a LVar is set: L:A32NX_AUTOPILOT_ACTIVE
I can add the Throttle in the bridge and flip the bit for this LED, but how do I connect that to the LVar?
I tried to map this bit to a sim var that is used in the plane, but that didn’t switch that LED. I’m not getting something here.
Or is there any possibility wo write to the device from an script in AAO?
Thanks in advance and thank you so much for this great tool!
Long time reader, first time post. So….
I have finally figured out how to get the the xtouch lights to follow all switch position in my JF PA-28s and have all functional knobs and switches working. Love the xtouch with AAO. Also built a GNS-530 emulator using Leo Bondar and buttons/switch and the dual encoders. I’ll figure out how to post the xtouch configurations and AAO scripts if anyone would like them. I am working on the Mooney M20 now. 
How exactly did you do that? Can you post a screenshot of your output configuration?
“this” meaning that some variables are stuck, while the switches etc. are still working? Sounds odd. Could be a script error and/or invalid simulator variable (the A: kind). Something that breaks the SimConnect data structures. There may be some information in the AAO logs, but if this is an error that happens inside the sim, there is no usable back channel. All the error information that we get from the sim is “oops, something just went wrong”.
How many numeric and how many string variables are we talking about? Maybe it is some kind of overflow.
Please make sure to always use the latest version of the AAO plugin with the StreamDeck.