Hello,

Thank you for your great product, can't fly without it.

Just wondering is it possible to also add the Just Flight RJ Professional to the WebFMC v2?

It is a really popular airliner.

Gr.

Robert

What about the one from the 146? I would half expect that to work for the RJ too.

(I don't have the RJ, so I can't be sure)

Thank you for your fast reply, I tried but it is a different kind of FMC.

Could definitely recommend you the RJ Professional also, it is like the BAE plus many extra's.
Also freighter coming out any moment

Yes, it looks different, but that doesn't mean that the screen won't work or that the key commands are different?

I was hoping that simmers would create their own packages eventually. The vol 2 FMC web pages all follow the same design structure, I tried to make it as easy to understand as possible...

 

I tried, but it does not work with the RJ. But can try make one, I am not really experienced with software coding though.

Edited August 29, 2025Aug 29 by rob0203

Here is how I do this:

1. Find a reasonably similar FMC that is already there, In this case maybe the one of the 146, and make a copy. 
2. Give the folder a suitable name - it forms part of the URL that you have to call 
3. Go into the cockpit and take a screenshot of the FMC. It is a bit of a struggle to get the camera straight over the device so it isn't distorted.
4. Edit the screenshot; cut oput the FMC, then cut a transparent hole into it, where the screen is going to be; save it to the Images folder using the name of the file that is already there (because that is already referenced in the HTML file!)
5. Edit the "cdu_cmds.js" file, enter the RPN code that is required to operate the buttons. 
6. Edit the "config.js" adjust the sizes and positions, and the camera move so it can automatically pop out the CDU. Check the name of the popout window and adjust it here if necessary
7. Then run AAO "As Administrator" in Offline Mode and call up the new FMC
8. Open the HTML file in an editor of your choice (I am using Notepad++)
9. Adjust the button positions. For that I set all borders of the <input> tags to "white", so I can see them, and then adjust size and position.
10. Make sure that the screen fits properly, if not, adjust in "config.js" and reload (personally, I disable the "popout" function while doing this, so all the page does is reload the contents)

That is pretty much it. When you have done this a couple of times, making a new FMC takes about two hours. If you've never done it, give it a day or two. 

 

 

Edited August 31, 2025Aug 31 by Lorby_SI

OK, seeing that JustFlight had a discount on the RJ, I bought the plane and will look at the CDU

Next time somebody requests a WebCDU I want a gift card in return... 😏 
 

Edited August 30, 2025Aug 30 by Lorby_SI

Oh great news! I use a profile to use the keys on my MCDU Winwing, I'm just missing the screen export. That's really the problem with this addon. Everything peripheral is really complicated to configure and my knowledge... Let's not talk about it 😄

Sorry, double post 🙂

Edited August 30, 2025Aug 30 by D1git4l

The RJ WebFMC has been added to the "WebFMCs Vol 2" package v2.4

I'm not totally happy with it though. Sometimes it is missing keystrokes. This model uses the IMHO worst control option of them all - LVars. For each key you have to set an LVar to 1 when the key is pressed, and then reset it to 0 when the key is released. Since changing the value of a variable does not create any "notification" or "event" in the sim, there must be a polling process in the aircraft logic that is constantly checking all (!) the LVars of all (!) buttons/levers/knobs in the cockpit and determine if they have changed - and then react to that. Since "constantly" is not possible, this mechanism obviously has a certain frequency at which it is executed. This can apparently collide with the frequency that AAO is executing scripts, and keystrokes can get lost - because the aircraft misses the moment in time where the LVar is changing value. This even happens on the device in the cockpit, but not as often. At the moment, all inputs on the web page go into a stack, which is then processed one entry at a time, leaving a little pause in between. So technically, nothing can get lost and everything is sent to the sim in the proper sequence, giving it time to think about it. But it still happens too often that a button input is not accepted. It is the same with the 146.

If anybody has a good idea about how to solve this, I'm all ears.

Edited August 31, 2025Aug 31 by Lorby_SI

Thank you very much! Will try it tonight.

It is a great plane though, I have also the 146 and the RJ. The RJ is kind of different plane also.

Really a big thank you to you! I will try that !

I tried it but it does not popout the window on my tablet.

When I open the webfmc mainpage and click the RJ it goes to another view to popout but then nothing happens.

Tested again with the citation and there was no problem, I use MSFS2024.

I tested without Air Manager and without MSFS popout panel manager.

Maybe it does not find the correct clickspot on my system?

Edited August 31, 2025Aug 31 by rob0203

I got it working with tracking the mouse position in AAO and changing it in the config,js file.

Thanks again for adding this!

 

1 hour ago, rob0203 said:

I got it working with tracking the mouse position in AAO and changing it in the config,js file.

Thanks again for adding this!

 

Strange. What's the resolution of your monitor? MSFS in Fullscreen mode or windowed?