I tried this and it didn’t work…not sure if its a piper thing that uses separate LVARs or something
Did you search for those LVars with AAO? When the plane is loaded, go to Scripting->Read LVars from sim. Then go to the script editor, press “Insert Variable” and check the list of “Local simualator variables”. Maybe you can spot something.
I still don’t understand the original script though.
What is
(L:HSI_crs,·Number)·1·+·+·(>K:VOR1_OBI_INC)
supposed to do? If “1·(>K:VOR1_OBI_INC)” doesn’t do the 1-degree-change, nothing with K-events will.
Haha I’m just going with trial and error. I’m trying to get to grips with the scripting! My original script made it move by 10 degrees! 1·(>K:VOR1_OBI_INC) also only makes it move by 10 degrees
These are the LVARS related to the HSI above
(L:HSI_CRS_knob,·Number)·1·+·dnor·(>L:HSI_CRS_knob,·Number). This works when i press test, it shows the value increasing everytime press test but then it doesn’t actually move the needle in the sim…
only makes it move by 10 degrees
Then controller input acceleration is active in MSFS. Is there any button that is pressed continuously in your setup (and not routed through AAO, which should prevent that).
Anyway, those LVars could be animation variables. Even if you get the knob to move, you still need to adjust the actual simulator variable, or the change is only a visual gimmick on the gauge.
I really wish developers would document the variables that can be used for external access…
I just removed a couple of things I had set in the Sim from the Bravo but yeah still no change. I actually think this is quite possibly a Sim issue now, as even with the mouse I can only change it by 10 degrees. ie a single click still makes it change by 10.
Its not a massive issue, i was just trying to learn a bit more about scripting. The big one is tomorrow with the CRJ. Hopefully Aerosoft are a bit more forthcoming with these things
Sorted it, found some more things bound to my Alpha, now works as expected. Spent days on that lol
Yes this is new with SimUpdate3, a mouse click can not move a knob by 1° in the cockpit anymore. Thankfully I now have AAO and all my cockpit knobs mapped to … well knobs.
That sounds like the the „classic“ hardware acceleration bug.
If one switch on the bravo perma-sends a 1 signal this occurs.
The devs are aware of this and someday there will be a fix coming.
(Me as a Thrustmaster TCA User having the same problem)
Yeah I’ve got everything gpoing through AAO now and it works
Development Update:
AxisAndOhs 2.04 will be able to operate the thrust levers of the CRJ
The implementation is currently being tested.
I quickly checked CJR700 and looks like about everything is controlled via custom L variables. If anyone else bought that AC, maybe we could do some collaboration to collect and document correct variables, and create scripts etc?
@LorbySI
I installed your example plugin readme.aao.streamDeckPlugin to see how you assigned the buttons. Unfortunately I can only read the title but not the variables.
I have bought it and will probably end up trying to get it all to work. Happy to share what I can work out.
Unfortunately I can only read the title but not the variables.
You seem to have confused the two plugins. The button in your screenshot is from the AP plugin - all buttons are hardcoded in that one, there is nothing to see in the PI.
I quickly checked CJR700 and looks like about everything is controlled via custom L variables. If anyone else bought that AC, maybe we could do some collaboration to collect and document correct variables, and create scripts etc?
Even the thrust levers only react to LVars
- L:ASCRJ_TQ_THROTTLE_1_POS
- L:ASCRJ_TQ_THROTTLE_2_POS
Value range is from 0 to 500.
Note to all AAO testers:
Starting with build 2.04 b36 of AAO you can use a joystick axis/slider to send values to LVars via RPN scripts.
I made a script called “Scripts-CrjThrottle1” with this code:
“(L:Scripts-CrjThrottle1)·(>L:ASCRJ_TQ_THROTTLE_1_POS,·Number)”
(the first LVar is the script variable, it must have the same name as the script ID (which is “groupname-scriptname”)
Then I assigned this script to the thrust lever on my old CH-Throttle. Note the “Axis min” and “Axis max” values!
Again - you need AAO 2.04 b36 or later. If any of the current AAO 2.04 testers wants to try this, please contact me again.
Other LVars:
- Variable to increment the heading bug: (>L:ASCRJ_FCP_HDG_CHANGE,·Number)
- Variable containing the current selected heading: (L:ASCRJ_FCP_HDG_INFO,·Number)
- You may want to run an automated aircraft script to sync the LVar with the actual simulator variable:
- (L:ASCRJ_FCP_HDG_INFO,·Number)·(>K:HEADING_BUG_SET)
ok thank you
If you are looking for examples, make sure to install the correct plugin, then get one of the profiles that Guenseli is providing on flightsim to. (search for “axis” on the .to site)
I know these examples 
thanks
By the way: What is the right syntax when I want to show or hide the ATC Window. The Event Name is “ATC”, but what is the Value? How to use the ATC commands (K:ATC_MENU_0)??
I’m having an issue as well, maybe 2.04 will help. I had to change the firewall port(now 6080). I changed the port in main.js as well. I’m using the CJ4 profile from flightsim.to. After changing the port all the gauges start working but none of the buttons do. If I click the button, the switch will flip and then go back to the state that it is in in the sim. So it is talking to the sim but it doesn’t seem to be receiving any of my inputs. I’ll email you my proof of purchase.
The issue with the current/public version of the AAO StreamDeck plugin is, that the WebAPI port is present in all “*Action.js” files. You would have to change it throughout the plugin code.
In the new version 2.3+ there is only the settings.js to change.