RJ Professional

Thanks for the link! I’ll watch this tonight with a brew. Just had a quick look……so familiar when the camera zoomed into the various flight deck panels. Just Flight absolutely nailed this beauty. The RJ and 146 remain 2 of my favourite modules in the game.

Would like to second the request to enable displaying the FMC screen on external hardware. With the appropriate API and documentation, I would be able to add this feature to MobiFlight. Other MSFS addons make the contents of the FMC screens available either via a local HTTP server or through SimConnect's ClientData feature (SimConnect_RequestClientData and related functions). Could such an API also be provided for the RJ?

I've done that before! I found that ensuring the AT is off and the cycling the AP switches on the OVHD works.

It is possible for the state saving to get confused between updates, especially after large product updates which have a lot of changes, as the aircraft may be attempting to load a state that was only possible in a previous version of the product. One thing I'd recommend trying is deleting the StateSave.ini file from the relevant file directory, and it'll then regenerate the next time a flight is loaded with the RJ with the correct state saving options available. MSFS 2020 - MS Store: C:\UsersUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe LocalState\packages\justflight-aircraft-rj\work\PanelSave MSFS 2020 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-rj work\PanelSave MSFS 2024 - MS Store: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-rj\work\PanelSave MSFS 2024 - Steam: C:\UsersUSERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-rj\work\PanelSave Hopefully, that should resolve any issues you may be having with state saving. If you continue to experience any of the behaviour you have listed, could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support In the ticket, if you are able to provide any screenshots/videos that are relevant to what you are experiencing, as well as any steps on how the behaviour can be reproduced, then our support team will be in the best position to be able to further assist with this. Mark - Just Flight

@Mark Thanks. I will test it again over easter and see if the problem still exists. I‘ve read that there are some people reporting similar issues with other products and even default aircraft here: https://forums.flightsimulator.com/t/unable-to-click-some-items-with-the-mouse-in-vr/758216/32 Seems to be VR related and probably something for Microsoft/Asobo to solve, not you…

Gets us a free climb and descent.

I gave up in the end. It's a great aircraft but VR is clearly not a priority and it's just too unusable

Thank you for pointing to this. But it seems to be a different issue. Mine is only related to ILS approach where the GS signal just disappears at some point on short final. Will try to make a video

It's not their nav data to be giving out in updates like that. Navigraph gives developers one AIRAC cycle as a business courtesy, but ultimately owns the data.

I had the same problem but I believe I have now resolved the issue... I switched state saving OFF in the EFB Aircraft settings page. With state saving ON it everything seems to work until you change to a different RJ type, ie switching from a RJ70 to an RJ100. At that point the TRP and FD problems start. Using the same aircraft type seems to work. With state saving switched OFF I no longer seem to have any problems, regardless of RJ type selected. Hope that helps. I'm told that Just Flight are working on a hotfix, so hopefully that will be out soon.

Thank you for the detailed feedback. We have logged this with your other feedback, and our development team will review this ahead of the next update to the 146/RJ. Mark - Just Flight

Thanks, @gazdav787 I think I've found the cause. My code has the form 1·(>L:GNLU910_L_FMS_XXXXX_ANIM,·Number) (WAIT:150) 0·(>L:GNLU910_L_FMS_XXXX_ANIM,·Number) But in this case is not necessary to come back to 0