For some reason Bvars no longer work in MS2020. I have Chris_PU_A320’s latest version of his A350 profile for the iniBuilds A350, v3.1. Been using it since he released it. He just updated it yesterday again. I also have the latest version of AAO (4.54 b08) and the Streamdeck plugin. Chris has Bvars for all his stuff under the KEYS and RMP1 pages. Everything in there uses Bvars. None work. I have to change all of them to IE and then they work. I am on the latest MS2020 version (not the SU16 beta). I have confirmed that the lorbysi-content-hooks folder is in the main MSFS community folder. Looks like the last date any folder was modified in there was June 2023. The layout.json and manifest.json files show Nov 14, 2024.

i reached out to Chris via his Discord and said he tested his latest version and everything works just fine. Not sure if he tested in 24 or 20.

Guenseli uses IE so his stuff works out of the box. 

Is there something I am doing wrong?

Edited July 5, 2025Jul 5 by B777ER

1 hour ago, B777ER said:

For some reason Bvars no longer work in MS2020.

Since when exactly? When you updated to the latest profile? And is it all of the BVars or just the ones in the profile = for this specific plane? 

My usual test case is the external power cover in the C208: 1 (>B:ELECTRICAL_ExternalPower_1_Cover_Toggle)

(just confirmed that BVars are still working for me in 2020. But I am in both of the MSFS betas)

 

Edited July 5, 2025Jul 5 by Lorby_SI

1 hour ago, B777ER said:

I have confirmed that the lorbysi-content-hooks folder is in the main MSFS community folder

And it also hasn't been disabled by another app like Addon Linker?

The fallback for this module is using the AAO in-game panel (you can hide it), it will also process BVars should the "hook" fail.

3 hours ago, Lorby_SI said:

And it also hasn't been disabled by another app like Addon Linker?

The fallback for this module is using the AAO in-game panel (you can hide it), it will also process BVars should the "hook" fail.

How exactly would AOL disable it? I do use that, but I have been using that for as long as I have had AAO with no issues. That folder and the lorbysi-content-fippanel are both in the main community folder and show in purple in AOL along with all the other stuff I have in my main Community folder and all work without issue.

What is this in-game panel? I have the Lorby-ATC-Bridge in my MSFS toolbar. Is this AAO in-game panel something else? Sorry, not familiar with that. 
 

Regarding when this started, it started when this thread kicked off below. So far it is just this plane and profile. But Chris stated it works on his end with Bvars in MS2020 thus leading me to believe it's an issue on my end. 

 

Edited July 6, 2025Jul 6 by B777ER

Ok, did some digging, looked at Chapter 8. I do have the AXISANDOHS FIP PANEL but when I run MSFS, the window comes up and it is saying, "Not Found" inside the window when I load into MS2020 and start AAO. I have confirmed that the lorbysi-content-fippanel is in the main community folder. I have confirmed there is a white border around the icon in the menu and the red border goes away. I don't want to uninstall/reinstall AAO as I don't want to lose all my setting and scripts. I have tried installing the latest version again over top of what I have and that did not work.

I looked at the WebFIPs Port and it is showing 8080 with my local IP. The WebAPI Ports are 43380 and 43381 with local host. I do not have a firewall on. What should I do?

EDIT - I think after about 45 minutes of troubleshooting, I solved the issue. I hit the default button under Tools - Configure WebFPI Port and hit the default button. The port changed to 43280. I hit apply and now after loading back in, the "Not Found" message has disappeared. 

 

Edited July 6, 2025Jul 6 by B777ER

8 hours ago, B777ER said:

So far it is just this plane and profile

Then it must be something in the profile itself, right? I have no idea how they are structured, maybe an issue with the scripts? I can't see how this has anything to do with the AAO app itself when it only affects this one profile. A reinstall won't do anything. Actually, a reinstall never does anything with AAO. It only replaces the executables, not the database. You could delete the database etc. manually, but then you have to reassign absolutely everything from scratch again.

You will find a chapter about the in-game panel in the AAO manual. But this would only be required when the BVars stop working for good, in every aircraft.

Edited July 6, 2025Jul 6 by Lorby_SI

6 hours ago, Lorby_SI said:

Then it must be something in the profile itself, right? I have no idea how they are structured, maybe an issue with the scripts? I can't see how this has anything to do with the AAO app itself when it only affects this one profile. A reinstall won't do anything. Actually, a reinstall never does anything with AAO. It only replaces the executables, not the database. You could delete the database etc. manually, but then you have to reassign absolutely everything from scratch again.

You will find a chapter about the in-game panel in the AAO manual. But this would only be required when the BVars stop working for good, in every aircraft.

Not sure if you saw the reply just above your reply here. It was a port issue.

8 minutes ago, B777ER said:

Not sure if you saw the reply just above your reply here. It was a port issue.

The issue is that you shouldn't have to use the InGame Panel. Something is not right with the Hook Module.

12 minutes ago, Lorby_SI said:

The issue is that you shouldn't have to use the InGame Panel. Something is not right with the Hook Module.

Wouldn't that be something then with AAO or is that something to do with that profile from Chris?

1 hour ago, B777ER said:

Wouldn't that be something then with AAO or is that something to do with that profile from Chris?

• When BVars (and other stuff with them) stop working for good, for every aircraft and in every situation: something is wrong somewhere in the app.
• If, as you said, the BVars only don't work for a specific aircraft in a specific use case, then it can't be the app. It must be something with the aircraft or the profile.

Maybe the plane uses another addon that prevents AAO from working properly? I remember that there were conflicts regarding the hook module with another app, but I don't remember which one it was.

 

49 minutes ago, Lorby_SI said:

• When BVars (and other stuff with them) stop working for good, for every aircraft and in every situation: something is wrong somewhere in the app.
• If, as you said, the BVars only don't work for a specific aircraft in a specific use case, then it can't be the app. It must be something with the aircraft or the profile.

Maybe the plane uses another addon that prevents AAO from working properly? I remember that there were conflicts regarding the hook module with another app, but I don't remember which one it was.

 

Interesting, I wonder which app it was. I have a few that run in the background with this plane. I run Mobiflight, TrackIR, GSX, Elevatex, Simlink for Navigraph, SteelSeriesGG for my headphones, Flight Tracker Stream Deck (required for Chris profiles), Steam, iCUE for computer fans and that’s it. 

14 minutes ago, B777ER said:

I wonder which app it was

It was a simulator addon that tried to use the same method as the AAO hook does - both cancelled each other out. I had a brief exchange with the author, but I cannot find it anymore.
Mobiflight killed the AAO MIDI interface a while back. I would recommend to not use multiple apps that essentially do the same thing. That is always bad. 

iCUE can be problematic because it pretends to be a game controller, causing an error in AAO. Make sure to put it on the blacklist in AAO. Use "Hardware -> Device blacklist", move everything into the list on the right with the "Ignore" button that isn't a game controller. That includes the StreamDeck btw. and all keyboards and mice.

I'm also not a fan of mixing several StreamDeck plugins in the same profile, but that is probably just me.

Every SimConnect client and addon that is running alongside the sim will degrade performance a bit, could cause stutters etc.. May be hardly noticable, or very much so. It is the cumulative effect that one has to watch out for. And they all may cause a conflict with each other. That is just IMHO of course. In your case you already have a minimum of 7 obvious SimConnect clients running there (including AAO which in itself runs multiple SC clients). Plus any internal logic that the plane may have that also uses the SimConnect API. But I would still call that a conservative setup. 🙂

Finding a fault with the hook module would require a trip to the MSFS developer mode and checking the "Console" if it shows an error of some kind. But again - when it is only one plane that causes trouble, you don't go searching for a systematic issue. AAO doesn't care about individuals, it is just a translator between the outside world and the sim.

Edited July 6, 2025Jul 6 by Lorby_SI