I'm fairly new to AAO, but have been experimenting with the Vision Jet on MSFS 2020.  I found a listing for map range zoom options on the display on a website stating the the HTML simulator events work for that.  I discovered that the "AS3000_TSC_Horizontal_BottomKnob_Small_Dec: 1 (>H:)" and "Inc" worked for this function, including testing it with "test with 0" and "test with 1."  However, the following day (nothing changed on my end with the simulator or AAO), those events stopped responding (I first discovered as I had a streamdeck button assigned to them).  Using the exact same "test with 0" option as the previous evening, the map was not zooming in or out like it did the previous evening.  However, that same knob has the function "AS3000_TSC_Horizontal_BottomKnob_Push: 1 (>H:)" that still responds perfectly.  After many attempts, reloading the simulator, AAO, rebooting, etc, suddenly one of the options began working again, but not the other (e.g. DEC worked but not INC while the Push bottomknob still worked and responded in the sim).  But, after starting another flight, it stopped working again (while the Push command still worked with the same knob).  I don't know if this is something with AAO or the actual Vision Jet on MSFS, but it is odd to me that it worked perfectly once and then stopped (I've been testing with the "select simulator event" window and each time the Push command works fine still).  Any help is appreciated.

3 hours ago, onridge said:

Any help is appreciated.

Sorry, no idea. 

Is it really the variable that is not being transmited or is it the StreamDeck button that doesn't work? Did you try assigning it to a button on a different hardware? 
What happens when you Scan for LVars in this state (just to check if the interface to MSFS is still working).

Are you certain that this is in fact the control that you should be using? Because those two HVars are actually the MSFS default.

Quote

13 hours ago, Lorby_SI said:

Sorry, no idea. 

Is it really the variable that is not being transmited or is it the StreamDeck button that doesn't work? Did you try assigning it to a button on a different hardware? 
What happens when you Scan for LVars in this state (just to check if the interface to MSFS is still working).

Are you certain that this is in fact the control that you should be using? Because those two HVars are actually the MSFS default.

I have been testing this lately without stream deck, just as a key down event pop up window, then the "select simulator event" window where it lists HTML variables (that is where I first discovered it worked using the "test with 1" and "test with 0" option after reading that someone else had luck with map zooms in HTML variables).  Before, whenever it worked with the "test" button in AAO, it worked with streamdeck (and when not working with "test" in AAO, it wasn't working in streamdeck).  So, I have been testing without outside hardware as the "test with 0" and "test with 1" are no longer triggering it like before.  The horizontal_bottomknob_push in the HTML simulator event continues to function/trigger a response in MSFS using the "test with 0" and "test with 1" option.

I do not know myself whether that HTML variable is the main control for the Vision Jet MFD range increase/decrease that the makers of the aircraft use (nor do I know how to find it for sure).  I just lucked into trying it the first few times and found it triggered the response in MSFS, then didn't work the next day (and only occasionally worked despite the aircraft being in the same state with the MFD displaying the map currently--for instance, at one time the zoom (range decrease) or decrease action worked while the range increase action did not trigger despite being similar commands.

When I scan for LVars in this state, it states "collecting LVars please wait" and then "LVars collected" after about 4-5 seconds. 

I'm definitely not a computer expert, so sorry if any of my explanation doesn't make sense.

 

**Solved** (I think).  Adding a number 2 (for the second garmin in the row of 3 in the aircraft) caused it to function as desired:

"AS3000_TSC_Horizontal_2_BottomKnob_Small_Dec: 1 (>H:)"

I'm not sure if the reason it worked on and off before was because no number was placed between Horizontal and BottomKnob or not.  I discovered a discord for the SF50 Vision Jet, found the suggestion of adding the number, and manually input a custom event which causes it to trigger as desired.