Hello,

I downloaded and installed the latest version of the A300 WebFMC (v2.5 last updated 26.12.2025) and I installed it as per the instructions and all the buttons work fine but the screen remains black despite trying so many things. I can confirm the FMC can be popped out in MSFS2020 but for some reason the screen is remaining black within the WebFMC page.

http://localhost:9081/webapi/a300/index.html

I have the following WebFMCs working fine: 787, iFly 737, PMDG 737, PMDG 777. Only this A300 FMC is causing trouble with the screen.

Can you please help?

Thank you.

Try popping out the FMC manually first, then call the web page.

6 hours ago, Lorby_SI said:

Try popping out the FMC manually first, then call the web page.

I tried that and no luck. The FMC buttons work but the screen remains black. What do you propose? Thanks.

Sorry, no idea. Working fine here with the inibuilds model. Different A300? Modded maybe?

Edited April 21Apr 21 by Lorby_SI

11 hours ago, Lorby_SI said:

Sorry, no idea. Working fine here with the inibuilds model. Different A300? Modded maybe?

No I don't have any mods. I am going to try the 787 or the iFly and see if their respective FMCs work fine or not. This will allow us to figure out whether it's an A300 problem or an AAO problem that I need to fix. Thank you and will revert back.

Ok so I tested the b787fmc and it's working fine: both screen and buttons.

I opened my Web API address window in AAO and the following is listed there. Do you see anything wrong?

Web API Ports: 9080 and 9081

http://192.168.1.120:9080

StreamDeck Plugin-> IP:localhost, Port: 9080

lorbysicontent-fippanel-> IP: localhost

lorbysi-content-hooks-> IP: localhost

zzz-lorbysi-aao-b787fmc-> IP: localhost

I am suspecting the following line of code in the config.js file

 

// Set the cockpit camera to a view that shows the MCDU
const campos = "2 (>A:CAMERA STATE, Enum) 2 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 22 (>A:CAMERA VIEW TYPE AND INDEX:1, Enum)";

Maybe because I may have changed something in my custom camera views for the A300 that this is not working. Could you maybe guide me as to how to update this line of code to match the new camera view that shows the MCDU? I use MSFS Panel Pop Out Manager so maybe the names of the views there can help me correspond the MCDU view to the numbers/variables used in this line of code?

Thanks.

1 hour ago, xsever said:

I am suspecting the following line of code in the config.js file

 

// Set the cockpit camera to a view that shows the MCDU
const campos = "2 (>A:CAMERA STATE, Enum) 2 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 22 (>A:CAMERA VIEW TYPE AND INDEX:1, Enum)";

Maybe because I may have changed something in my custom camera views for the A300 that this is not working. Could you maybe guide me as to how to update this line of code to match the new camera view that shows the MCDU? I use MSFS Panel Pop Out Manager so maybe the names of the views there can help me correspond the MCDU view to the numbers/variables used in this line of code?

Thanks.

That would only mean that the web page cannot pop out the screen on its own. The only way to figure that out is trial and error. Be mindful of the mousepos too. What the web page tries to do is call up a camera view that includes the CDU, then place the mouse in the middle of the CDU and pop it out for you.

But when the web page also can't find the instrument that you have popped out manually, then one explanation would be that the name of the popout window is different from what it should be. That's in the line above, "popname = ". It expects the window to be called "WASMINSTRUMENT". If your manager app changed that name, you will have to change it here too.

14 hours ago, Lorby_SI said:

That would only mean that the web page cannot pop out the screen on its own. The only way to figure that out is trial and error. Be mindful of the mousepos too. What the web page tries to do is call up a camera view that includes the CDU, then place the mouse in the middle of the CDU and pop it out for you.

But when the web page also can't find the instrument that you have popped out manually, then one explanation would be that the name of the popout window is different from what it should be. That's in the line above, "popname = ". It expects the window to be called "WASMINSTRUMENT". If your manager app changed that name, you will have to change it here too.

Thank you for the response. The first thing I noticed in the code and I double-checked is the "WASMINSTRUMENT" and it matches 100%. I must clarify that I never use the pop-out manager to pop out the FMC. I only did that as a test to see if it's popping correctly.

As you said, I am going to do some trial and error to figure out all these variables. I will revert back.

The funny thing is that I've been doing all of this in MSFS2020. I launched MSFS2024 which is still relatively vanilla and tried this and I got the same result. The FMC screen remained black.

I had some time to dig deeper into this with the hope of diagnosing the problem.

I first assigned a button to "2 (>A:CAMERA STATE, Enum) 2 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 22 (>A:CAMERA VIEW TYPE AND INDEX:1, Enum)"; and when I press it, I get a camera view that shows the CDU. Ok so that's good until here.

I then used the mouse cursor position feature in AAO to get new x and y values that match my 1080p monitor and I then updated these values in the config.js file and saved it. I thought this would fix the problem but it didn't.

I can still manually pop out the window fine, it is called WASMINSTRUMENT for sure, the buttons work, but not the screen.

Is there a way we can modify the config.js code whereas it relies on a manual pop out of the window rather than popping it itself? I'm asking this because when I call the index.html file and the buttons work, the actual popping of the CDU window does not occur.

Thanks.

I tested the iFly 737 web FMC and initially the same problem happened where the buttons worked but not the screen. I went into the Aircraft automated scripts and selected IFLY_737MAX_CDU (Repeating and One shot - Beginning) and added it and then the screen was displayed all of a sudden. Problem solved.

Now I can't find a similar aircraft automated script for the A300. Am I missing it or what is actually happening here? Is this because I'm using MSFS2020?

Edited April 27Apr 27 by xsever

1 hour ago, xsever said:

Now I can't find a similar aircraft automated script for the A300

There is no such script. A300 uses popout, iFly has a native interface. Completely different technologies.

1 hour ago, Lorby_SI said:

There is no such script. A300 uses popout, iFly has a native interface. Completely different technologies.

But the config.js file for the iFly 737 Max is structured the same as the A300.

1 hour ago, xsever said:

But the config.js file for the iFly 737 Max is structured the same as the A300.

That file is for the EFB, not the CDU.

The iFly has its own SDK, similar to PMDG. The script is there to tell AAO to collect the data from that SDK. 

The A300 has neither - no SDK, no script. With this plane (and most of the other Vol2 WebFMCs), AAO wants to capture and stream the popped-out window showing the CDU screen. It also moves that window to a position outside your screen, so it won't cover your simulator. Apparently, something about this process is going wrong on your computer, but I don't know what that could be, sorry. I would probably take a look at the error console/developer tools of your browser, maybe prevent the move off-screen (global.js WINDOWPOSITIONSET) to see if the popout is there in general, or even try a different browser altogether. For example, old-er iPads cannot display HTML5, that has tripped up some people too. 

Normally, when the CDU cannot be popped out automatically, you do it manually, and then refresh the web page (F5). 

Edited April 27Apr 27 by Lorby_SI

I tried so many things and nothing worked but 30 mins ago, I was able to resolve the issue and I think I did it by copying the global.js file that was in Documents\LorbyAxisAndOhs Files\WebPages and pasting it in Documents\LorbyAxisAndOhs Files\WebPages\a300

When I did that, the screen appeared and everything worked like a charm.

I got this idea by analyzing the contents of the index.html file and seeing that it calls for the globa.js file so I placed it in the same directory and voila.

Could that be it or am I imagining things here?