2 hours ago, xsever said:

Could that be it or am I imagining things here?

The package has not been installed correctly, part of the path is missing. No wonder that it didn't work.

The correct path is this one, exactly like it is in the ZIP file:
\Documents\LorbyAxisAndOhs Files\WebPages\fmcs\a300

only then all parts are in the correct location.
 

Edited April 27Apr 27 by Lorby_SI

1 hour ago, Lorby_SI said:

The package has not been installed correctly, part of the path is missing. No wonder it didn't work.

The correct path is this one, exactly like it is in the ZIP file:
\Documents\LorbyAxisAndOhs Files\WebPages\fmcs\a300

only then all parts are in the correct location.
 

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.

53 minutes ago, xsever said:

Would you happen to know why that is?

No, sorry. I programmed a flight at EDDF 20 minutes ago and took off towards LIRF. The buttons still behave the same as they did at the beginning. They are not the fastest, mostly due to the low update rate that has been set in the WebFMC. About 8 times per second or lower, so it doesn't overload AAO's network API. As long as you didn't change the resolution or the size of the captured window, that should work fine. But this popout technique puts a significant strain on the network, your computer and the sim, no doubt about that.

Be mindful that you cannot compare this to the iFly or the PMDG WebFMCs. Those use completely different techniques, and they are a lot less performance intensive.

Edited April 27Apr 27 by Lorby_SI