RJ Professional

Found it next to the FMS CDU, don't know how I missed it.

Thank you both.

I am having the same problem, did anyone manage to work out how to solve the problem without having to start the flight again?

I also have this issue, no speed indication and the barber pole on the PFD. The speed on the standby indicator is working fine. I don't have ice effects turned on in MSFS2024 and I have probe heaters on, on the aircraft. This is my 2nd flight today, first one with the RJ85 and I had no issues. This flight is on the RJ1H, and in-between flights I went back to the main menu in MSFS2024 before starting.

Just found out you can use 'DEL' on the row above the mistake, this then removes the error.

@Mark further information on this. When pressing esc for the sim menu (even briefly) and then resuming flight: CMPMSTR warning autopilot panel appears to completely loose power and then comes back on autopilot disconnect warning (can be silenced with two clicks on disconnect) autothrottle disengaged with IAS reset to 100knts to recover I must: cancel the AP disconnect warning (this causes the MCP to go completely dark for a second and then power on again with IAS at 100) reset IAS to cruise/climb speed turn off the FDs and turn back on -wait approximately 20 seconds (nothing will happen until i wait) re-enalble autothrust re-enable AP, Lnave and either LVL CNG or ALT So I CAN get the airplane back. The symptoms of it are almost akin to someone pulling the fuse on the MCP module forcing it into a reset from power off. recreation advice i had continuous ignition armed - this may be why the engines came back as they seem to spool down/shut off - i've had situations where the engines would not restart ensure APU is OFF ensure you are in climb phase (climb power / above 10,000) repeating ESC to menu and resume a number of times to see if you can recreate the bug I have captured a video below: video of bug - RJ100 - MSFS2020

Thank you for pointing me in the right direction.

reporting back - thanks @Flight0101010101 - I definitely think it was keybindings on my numeric pad which caused the issue. Once I removed all flight control bindings from the numeric pad, I have flown without issue. @Mark sorry about the red herring but I do think it would be worth it to call this out in documentation.

@Kimchoc Can you let us know your support ticket number and we can look into why it hasn't had a reply.

I have individual toe brakes mapped for each brake mapped to the MFG Crosswind, but i am not experiencing any abnormal brake actuation on take off roll, and the brakes do not look engaged at all. The pressure releases normal on the ground as well as i was trying to figure why it was doing that

@Martyn No this was direct from yourselves. Also yes I'm using v1.3

Both our SimBrief profiles (which should be the default ones) and the aircraft EFB use a standard passenger weight of 170lbs, so it should all match up. Whilst the SimBrief profile can be edited to a different value, the aircraft EFB cannot.

Following up. In my case, when I was trying to intercept ILS RW05, it was indicating BKCRS on the right side of the PFD, leading me to believe that this was a Back Course ILS, which I'd sort of heard about but have never tried (no, I'm not a RWP yet). The Locator bug was on the right when I expected it to be on the left, so I decided to switch to RW23 The conditions were LIFR, so I decided to switch to RW23, but also got the same weirdness. I somehow managed to land by hand-flying the LOC/GS bugs (Flight director was still directing me away from the approach course, so AP was no help). (If real-world, I'd certainly have diverted.) Did this same scenario a day later, same result. Did it yesterday, but realized previously that I'd tuned the ILS on NAV1, but had the Glasgow VOR tuned on NAV2 (FO side) just for additional DME data. This time they were both tuned to the ILS, and everything worked perfectly, both runways. Unsure if this is expected? With JustFlight, I'd be 90% sure this is by design and not a bug. I'll try this again tonight, maybe switching NAV2 between the ILS and VOR to see if this is really the cause.

You have to convert files to .mp3. If it's .wav, it will not work.

+1 this wound be nice

I can confirm that this issue has been logged and should be addressed in the next update.

Hi, thanks for tip but unfortunately no double bindings or comm assistance setting.

@RPGamerous Thanks for your post. You are right, they do work with the scroll wheel but not when clicked as with the 2020 version.