RJ Professional

Yes, the systems logic is identical in all of our aircraft in both MSFS 2020 and MSFS 2024. In the RJ, pressing one of the FADEC fault/off buttons will turn OFF the respective FADEC unit. Pressing it a second time will turn ON the respective FADEC unit (after a short delay). I have just tested this on my end in MSFS 2024, and it is working as above, so if you're seeing anything else, could I kindly ask you to raise a support ticket with Just Flight Support via the following link, and our support team will be able to assist with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

Looking forward to any improvements to the RJ in 2024. Overall I get better performance and enjoy the RJ better in 2024.

Tried it 2 times in SU3beta and it loaded both times properly with AT on and Green. so hoping that is was eventually adressed - by MSFT. Will report back with more feedback from todays new SU3beta

We haven't noticed any compatibility issues with the RJ following the release of Sim Update 2. Mark - Just Flight

Thanks @Mark easy workaround in the end. Appreciate your efforts in following this up.

I just wanted to chip in my recent observations. I managed to get quite a few fps by disabling the pax cabin via EFB. I did move gauge refresh slider to minumum. While refresh rate did not make any difference to me, disabling the cabin did. V-Synch is off, I double checked. The only thing I would like to kindly suggest to developers is to maybe consider decreasing texture size decrease to 4K as an option during installation?

Some of the early 146 aircraft, of which we operated a few, had separate high and low intensity nav lights installed, each powered by different electrical busses. The cockpit switch was 3-position: HIGH-OFF-LOW.

Thanks for the info Mark

Thanks Mark... The panel lights assignment on my Bravo was the issue... All good now... Cheers! Rob

Unfortunately maps not working in the newly updated Warrior and Turbo Arrows either... at least for me... [image: 75365898-6bcd-4eab-bbec-2e24d8351532.jpg]

Glad I found this post. I have been banging my head on the table trying to understand what I am doing wrong. Please fix this ASAP, it's a really awful bug. It has been 6 months since it was reported.....

Thank you for the kind words! I'll be sure to pass these on to the rest of the team. Mark - Just Flight

Nothing new to report on this from our side at the moment. It remains on our internal feature request list as something we would like to add in the future, but we aren't able to provide any time scales for when that may be. Mark - Just Flight

Thanks, #1 is exactly what I asked for and it works.

happy to report all user error (my fault) had the ign selector on the TM Airbus Throttle set to Crank. but it in normal position andd EGT spooled up

General advice, landing and taxi in, typically achieves 450-550C. Brake fans running on chocks after shutdown and before engine start must be for a minimum of 15 minutes. Typically, if you start up and taxi after a minimum of 20 minutes and can start the takeoff with brake temps at a maximum of 200C, all OK. There are tables within the aircraft manuals for calculating the required cooling period if brake fans or BTI are unserviceable. In service, on a hot day with a 30 to 40 minutes turnaround after a max weight landing on a 6,000’ runway, the brakes would be usually be found cool enough to start up and taxi out.