I have the demo version (trying before I buy (if i buy)) and im struggling with it mostly with the WebAPI port 9080 part. I cant seem to find it or figure out what causes the lack of communication between my Stream Deck Plus and MSFS. I dont see the "Enable Web API on port 9080" under tools. I have 3.00 b53 version. and the most recent stream deck software. any help will be greatly appreciated. I also use the Turtle Beach Velocity One as my yoke and throttle detent if ti helps. 

First of all, You running AAO as run as administrator??

53 minutes ago, Adrian123 said:

First of all, You running AAO as run as administrator??

yes. If im not running the stream deck software i get a 404 error when i go into port 9080 from local host. If im running it i get a local host refused to connect. This is for one im making on my own for the default a320 (i dont have the paid ones, i have FBW but dont fly it). I mostly want to use my stream deck for autopilot and switches/buttons (like groun power and dome light). 

6 hours ago, Cellblok69wlamp said:

I dont see the "Enable Web API on port 9080" under tools.

It is now called "Tools->Configure WebAPI port" The Web API is always active when you start AAO "As Administrator". There are two small green LEDs in the bottom right corner, indicating if the WebAPI is listening. But for any number of reasons (Firewall, AntiVirus, other Apps) your computer may not let the StreamDeck plugin communicate with AAO. On the download site there is the "WebAPI Troubleshooting Guide" PDF - this document applies here.

First step is always to change the port, 9080 is often already in use by other tools. Port must be changed both in AAO and in the plugin, the dialog does both. But the Elgato StreamDeck software cannot be running at that point, you have to shut it down (otherwise changing the port has no effect).

 

Edited May 26, 20233 yr by Lorby_SI

9 hours ago, Lorby_SI said:

It is now called "Tools->Configure WebAPI port" The Web API is always active when you start AAO "As Administrator". There are two small green LEDs in the bottom right corner, indicating if the WebAPI is listening. But for any number of reasons (Firewall, AntiVirus, other Apps) your computer may not let the StreamDeck plugin communicate with AAO. On the download site there is the "WebAPI Troubleshooting Guide" PDF - this document applies here.

First step is always to change the port, 9080 is often already in use by other tools. Port must be changed both in AAO and in the plugin, the dialog does both. But the Elgato StreamDeck software cannot be running at that point, you have to shut it down (otherwise changing the port has no effect).

 

That helped a lot. I have a minor issue (I think) where the web API isn't connected until I start and connect to MSFS. I don't know if that is normal behavior. Other than that it is working as it should.

25 minutes ago, Cellblok69wlamp said:

I don't know if that is normal behavior.

Yes it is. 

On 5/26/2023 at 10:25 AM, Lorby_SI said:

Yes it is. 

Ok. So far it's working well. I only can't figure out how to turn on the cabin lights (panels. flood) and the windshield wipers using my stream deck via Axis and Ohs for the Asobo a320.

2 minutes ago, Cellblok69wlamp said:

Ok. So far it's working well. I only can't figure out how to turn on the cabin lights (panels. flood) and the windshield wipers using my stream deck via Axis and Ohs for the Asobo a320.

I only have a bunch of really old scripts for that, and only the wiper script is still working, sorry:

Wiper left toggle
0·1·2·1·(L:WIPER_left_var,·Number)·(L:WIPER_left_idx)·4·iseq·(>L:WIPER_left_var,·Number)·(>L:WIPER_left_idx)·0·(L:WIPER_left_var,·Number)·==·if{·(>K:0·-·A320-WIPER·LEFT·OFF)·}·1·(L:WIPER_left_var,·Number)·==·if{·(>K:0·-·A320-WIPER·LEFT·SLOW)·}·2·(L:WIPER_left_var,·Number)·==·if{·(>K:0·-·A320-WIPER·LEFT·FAST)·}
 

Maybe check the developer mode in MSFS, Tools->Behavoirs. Hover the mouse over the knob or button in the VC that you want to access and press Ctrl&G. The associated code should come up in the behavior dialog.

Or visit flightsim.to, I think that there are a bunch of StreamDeck profiles, templates and script collections, made by talented simmers.

 

7 minutes ago, Lorby_SI said:

I only have a bunch of really old scripts for that, and only the wiper script is still working, sorry:

Wiper left toggle
0·1·2·1·(L:WIPER_left_var,·Number)·(L:WIPER_left_idx)·4·iseq·(>L:WIPER_left_var,·Number)·(>L:WIPER_left_idx)·0·(L:WIPER_left_var,·Number)·==·if{·(>K:0·-·A320-WIPER·LEFT·OFF)·}·1·(L:WIPER_left_var,·Number)·==·if{·(>K:0·-·A320-WIPER·LEFT·SLOW)·}·2·(L:WIPER_left_var,·Number)·==·if{·(>K:0·-·A320-WIPER·LEFT·FAST)·}
 

Maybe check the developer mode in MSFS, Tools->Behavoirs. Hover the mouse over the knob or button in the VC that you want to access and press Ctrl&G. The associated code should come up in the behavior dialog.

Or visit flightsim.to, I think that there are a bunch of StreamDeck profiles, templates and script collections, made by talented simmers.

 

I'll look around for a solution. But most of the flightsim.to is for the FBW or Fenix. I do plan on learning the fbw but i mostly use the asobo for easier semi-realistic flights (less prep time).

I've taken a quick look around the default A320 code. Most assets seem to be BVars now, as was to be expected:
Example (left panel flood):
1·(>B:LIGHTING_GLARESHIELD_1_Inc)
1·(>B:LIGHTING_GLARESHIELD_1_Dec)

Make sure to read the part about the AAO InGame panel in the Manual when you want to use BVars. This will no longer be necessary in the next version of AAO (3.02), but for the time being you need that panel.

Edited May 31, 20233 yr by Lorby_SI

1·(>B:HANDLING_Wipers_Off)
1·(>B:HANDLING_Wipers_Slow)
1·(>B:HANDLING_Wipers_Norm)