RJ Professional

another feature I'd really like is for the Flight data computers (FMS) to be capable of displaying their outputs. So those of us with external hardware FMS's could use a program like spad.next to display on our hardware. Input is working, not output though.

The 146 and RJ both simulate cabin temperature based on the selected air source and temperature selections, and take into account factors such as if the aircraft is in direct sunlight, or if one or more exterior doors are open. We did make some minor improvements to the Air Conditioning logic with the 146 v2.4 update that will be brought across to the RJ in the next update, but that's primarily related to the DUCT TEMP / CABIN TEMP relationship and rate of change. Mark - Just Flight

I don't recall seeing any other reports of this, so 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 could provide details such as the simulator you're using (including which sim update), and if you have any steps to reproduce this behaviour (including screenshots/video if possible), then our support team will be in the best position to attempt to reproduce this and offer further assistance. Mark - Just Flight

There haven't been any changes to the IRS alignment or FMS logic recently (other than the addition of Simbrief Import in the v1.4 update). However, any feedback that gets sent to us always gets logged on our internal trackers, and we do consider everything each time an update is planned. The exact scope of each update is typically based on the availability of our development teams at the time of the update, so it's tricky to give timeframes for if/when certain bug fixes/features may be included in an update. Mark - Just Flight

We are aware of some scenarios where changing the simulator time (or using active pause) can cause the timers in the RJ code to go out of sync with the timers in MSFS 2024. We are investigating this, and we aim to have a fix implemented in an upcoming update to the RJ. In the meantime, we would recommend minimising any time changes or active pause usage when using the RJ in MSFS 2024. Mark - Just Flight

Maybe it's possible to tie the engine sounds to the values the PED uses instead of the engine simulation variables or calculate separate values specifically for the sounds. That way, you can do whatever you want underneath the hood while fixing the engine sounds. The best of both worlds.

Yes, my experience with both is that they have the same systems depth. The RJ may have EFIS, but don't let that fool you as there's no VNAV, only advisory VNAV (just like the real aircraft). The RJ is much more hands-on than for example the 737NG. Unlike the 146 it has autothrottle, but it won't select a thrust mode automatically like the 737NG would. The procedures are old school just like with the 146 (lenghty procedures with loads of system tests). So it's just a notch above a 146 with an EFIS retrofit. If you want a more hands-on airplane with EFIS that still has a decent autopilot, the RJ is an excellent choice. I prefer the RJ, but that's just my personal taste and not because the product is a better product than the 146.

Thanks Mark... Rob

@Mark - Thank you! That worked.

We're not aware of any compatibility issues between 146 Professional v2.4a and RJ Professional v1.4. Could I kindly ask you to raise a ticket with Just Flight Support, and one of our team will be able to assist with troubleshooting this: https://www.justflight.com/support Mark - Just Flight

If the BRK FANS switch is in the AUTO position, then power will be removed from the brake fans when the nose gear is not down and locked. However, even if the BRK FANS switch is in the ON position, the small, enclosed landing gear bay will slow down brake cooling, as there isn't really anywhere for the hot air to go. Mark - Just Flight

Thanks for reporting this. This is a known issue, and we do have a fix already implemented for our other airliners that will make its way into the RJ in the next update. Mark - Just Flight

said in ND Data and Alt hold small bugs: @awde Looks like the standard reply should have been sent out which is basically "we will log these issues and pass them to the dev team". This was done but someone probably forgot to reply. Apologies for that. Meanwhile, the dev team is aware and will be looking at what's possible to resolve in a future update(s). Thanks for passing it on.

I also experience a problem during initial climb with the airplane not accelerating from V2+10 to 210 kts. I'll test this further before creating a support ticket because I think there are some variables which might play a role (BeyondATC, takeoff procedure (normal, NADP), on TRK/HDK or following a LNAV SID, inappropriate engine derate), but this is what experienced last flight: The aicraft stayed at the same pitch after selecting a higher speed, activating LVL CHG didn't help either. Had to accelerate using VS before selecting flaps up. MSFS 2020 and BeyondATC. Just posting this here to indicate this might not be a MSFS 24 issue only.

Thanks for the feedback. This is something we have on our internal feature request tracker as something we'd like to improve in the future. Mark - Just Flight

Understood. Thank you.

Yup I would love to see this!