RJ Professional

The NAV light LOD behaviour isn't directly fixed by building a product as an MSFS 2024 native package, as the behaviour exists with the RJ, which post v0.1.4, is an MSFS 2024 native package. We do have some ideas on how we can work around the NAV lights LOD limitation, and we will be investigating them ahead of the next update to the RJ. Mark - Just Flight

If this behaviour occurs again, we kindly recommend that you raise a ticket with Just Flight support at the following link: https://www.justflight.com/support In the ticket, if you could include screenshots/videos of the behaviour, plus any steps to reproduce the issue, then that will give our support team the best shot at trying to replicate this behaviour, which can then be passed on to our development team if required. Mark - Just Flight

Correct, using Spad.Next.

It may be worth double-checking that there aren't any outstanding updates for the Thrustmaster software or the device drivers, and also checking if there are any sensitivity curves/deadzones applied within the Thrustmaster software itself. Unfortunately, with it not being our software, we're limited with what support we'd be able to offer for it, but if you contact Thrustmaster support, they should be able to provide some assistance and troubleshooting steps. Mark - Just Flight

It is good practice to allow the aircraft to level off at a preselected altitude before dialling in a new altitude. I don't recall if it's in the 146 or RJ FCOM (or both), but one of them does advise pilots not to adjust the preselected altitude during the altitude acquisition phase. From the input we've had from pilots, as well as various reference videos online, we find that pilots flying these older aircraft types spend more time thinking about passenger comfort than those flying modern airliners. For example, a lot of RJ videos online show pilots descending in V/S mode and slowly increasing/decreasing the VERT SPEED value rather than using LVL CHG mode. Even a relatively 'modern' looking RJ is a lot more involved than a modern airliner! Mark - Just Flight

Seeing this issue now in MSFS 2024 with SU3. Restarting the sim isn't fixing it either.

@Iconography That bug report for SU4 beta sounds exactly like what I am experiencing. I’ll probably go off the beta back to SU3. It’s interesting it only affects certain planes. Fenix A320 is fine for example.

I haven't seen that one before. Great find! Mark - Just Flight

Thanks for your response and explanation, I just hope that Just Flight's excellent written and video tutorials continue to be the best in the industry for beginners : )

Yes I should have replied earlier sorry when I discovered this. It is indeed an SU4 beta issue and affecting a whole raft of other products as well. No doubt will be resolved in due course.

Also having the same cursor issue in VR which is a shame as this is one of my favourite aircraft and I only fly in VR

This appears to still be an issue now in latest release

Sadly I am also getting this one which has rendered the RJ almost unusable in VR

Not sure I understand what your issue is, but on my Bravo I'm using PED_MID_Eng1_throttle_OFF with a value of 1 when going to the OFF position and 0 when turning on fuel. That has worked well. I believe I got this from another user, who also had some latch animation variables (which I omitted). I'll see if I can locate it. One thing that did cause me some trouble initially was messing with some other variables, then failing to restart the sim when trying something else. EDIT: This was the post that helped me: https://community.justflight.com/post/33830

Great news, many thanks for the update.

Are you overriding the A/T with your Throttle Levers/Quadrant? That could be fighting the system and not allowing it to come back to idle.

You can't display the WX or Terrain on the ND. They can only be displayed on the WX RADAR screen under the Engine instruments.

What Mark said