xsever

You're a saviour! Thanks a lot for pointing that out. I didn't know despite reading the documentation. Now that it is working, I noticed now that after a couple of minutes of using the web fmc, the input of data through buttons becomes very lagging and delayed. If I refresh the page and the script re-executes, the lag is gone for a couple of minutes and then it's back. Would you happen to know why that is? I faced a tiny bit of lag with other web fmcs but nothing this major.

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?

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

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?

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.

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 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.

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

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.

Winner winner, chicken dinner! This did it. Thank you so much. I will start with 30 and then experiment with 35 and 40 maybe later on and then using adaptive mode in lossless scaling to go to 60. I noticed in your screenshot that you're not running the latest version of profile inspector so I thought I'd flag that out to you. Thank you again! Any idea why the in-sim v-sync and frame limit options don't work for us?

Thank you for the detailed instructions. I am ready to pull my hair almost. I made sure my monitor is set to 60 Hz in Windows Graphics settings and then I double checked my settings in the sim and yes V-Sync is set to ON and Frame Rate Limit is set to 50% and for some reason the FPS are not locking to 30 and are going as high as 60 sometimes. Very weird! Is there anything else you could think of? Thanks.

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

I enabled Vsync and set the frame rate limit to 50% so I can get 30 FPS out of my 60 Hz monitor and I applied the setting but that did not result in a locked 30 FPS. The FPS kept fluctuating above 40-50 FPS as if I did not just enabled Vsync and set the frame limit to 50%. Is there anything wrong with what I did? Any idea why this didn't work? Thank you.

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.

I've been using this app for a long time now and it's just flawless so thank you. I finally installed MSFS2024 last week and started flying with it and this app works very well with it. What I like the most is how the built-in frame limiter and the dynamic settings frame limiter work with the app's FPS cap. Since I still use MSFS2020 as well, I must ask: is there any way in MSFS2020 to natively hard limit the FPS of the sim just like MSFS2024 does to ensure stutter free stable frames at like 40 for example? Maybe a line of code inside a cfg file or something? I find this to be the best thing about 2024 in terms of performance. Thanks!