WF971

(It feels anachronistic to me because my nostalgic attachment to the aircraft is based on 80s-90s Twin Otters, with much more traditional radio navigation equipment. (just to clarify.)

Have you set Icing to Visual Only in the settings? It was a bonkers problem for the CRJ so I've had visual icing only since buying that product.

I VERY much support this! Especially if changing out the Garmin for an older stack isn't workable. (Which honestly I'd pay dollars for. The Garmin is hell on my eyes and feels anachronistic)

Thank you kindly!

I believe this has yet to be solved. If anyone knows it to be a CRJ feature then by all means clue me in. I didn't check whether there is still 'jumping', I just confirmed that values are still in the wrong places. In the first picture the PFD's yellow VOR2 course (355) is different from the MFD's yellow VOR2 course (298). That's because the PFD course is using the copilot's CRS2 value.

The AOM Part 2, page 5-1-105 and -106 describes the function of the radio's DME function. I don't know how real pilots usually do things, only my own 'procedures'. I'm referring to the radio tuning unit on the middle console, left part. Where you fiddle with TCAS etc. By clicking DME-H on an active, tuned NAV frequency you should get the DME info in the PFD and MFD. (I haven't flown for a month or two but that's how it worked back then IIRC).

As of 05 this does not appear to be resolved. A quick glance at the NAV SRC of the PF/PM, and a glance at the frequencies for NAV 1 and 2, should illustrate that the crossed wiring persists. There is one snag related to reproducing this: So long as both signals are received it is possible to experience a certain flicker between the PFD's functionality, such that they momentarily appear to behave correctly. For the majority of the time though, especially if you wiggle around the frequencies for NAV 1/2, it should be readily reproducible.

The report was lodged here. I did not think it worthwhile to go into full details for the OP's purposes. 😃

I've had some issues with manually setting localizers personally so I can't say it's bug free. However, to manually set the course for the CDI rose in the event of an ILS landing you need to get around some of the plane's automation. First identify on your left the NAV SOURCE knob. Then, on the glareshield, identify the CRS1 knob above FD. On your center console, the display of the FMC. Additionally, by your thigh identify the Backup RTU and the associated FMS TUNE INHIBIT switch. First, ensure NAV SOURCE is set to NAV1/VOR1/LOC1 (green text). Not FMS1 (white) or FMS2/VOR2 (yellow). Second, on the FMC select Radio, then for NAV1 select MODE to MAN. This should circumvent the autotuning behaviour. Finally input your desired frequency in the entry field just above. Third, on the glareshield, turn the CRS1 knob to set the ILS course. CRS1 is for nav1, CRS2 on the FO's side is for nav2. Nav2 in my experience doesn't quite work. Fourth and optional, down by the backup RTU, flip the FMS TUNE INHIBIT switch (towards the text). I'm unsure whether this is a necessary step so long as the Backup RTU is not in fact active, or how its logic interfaces with the MAN/AUTO mode in the primary RTU. Sorry. Volume 5 of the manual, pages 5-1-101 to -117 are very handy for learning more about this.

This is not FMS related, I think? I could be wrong but perhaps it's best to create a separate thread for this. I think perhaps the notification "Do not create lists" is intended to un-tangle tangles like this.

Being brutally honest, CRJay's PFD would make life a lot easier for me. This is an extremely eye-straining cockpit, even for someone using trackIR. If I recall correctly, popping out panels was linked with CTDs since release. I've therefore not wanted to experiment with the option.

I personally feel as though the aircraft notches 10-12kt low of the approach speed while behaving jittery at the EFB-provided speed. That aside, which is probably brought on by poor airmanship, the overall experience is now remarkably smooth.

I too encountered engines suddenly disappearing on me and the flight plan going missing. I had touched a dial/rotating knob that I assigned to spoiler axis, and thought sudden hydraul loss was the problem. Not exactly correct. The same knob had been assigned to the fuel mixture, back when I used more prop planes. Turned to zero, this 'knocks out' the aircraft. Rotating knobs being what they are, even a small bump of the throttle is enough to make it jump from e.g. 41% to 42% and possibly back and forth. If you load your flight with the mix knob turned to 0%, the aircraft will first pretend you have it at 100% until it is bumped up or down. If you have an axis with prop control/fuel mix assigned, you could wiggle the knob and see if you can reproduce these results. My solution was to delete the mix assignment; I'll restore it if I fly another airplane later.

Hello. I did not find this issue brought up in the general chat, nor in the other support threads. (Thankfully there weren't too many to search manually). With the exception of CRS2 selector knob, I am referring to the left-hand side of the cockpit PFDs here. I've not done any checks on the right set of PFDs. Expected behaviour: With all systems nominal; setting NAV 2 for a VOR frequency in range which is NOT shared by NAV 1; selecting PFD NAV SOURCE to NAV 2; and adjusting CRS2: 1) the PFD compass roses should change their orientation, 2) the CRS value in PFD should change, and 3) the centerline changes its position once we are near/over the correct radial. Observed: The compass roses will not change their orientation, only the right PFD CRS value changes its value, and the radial is never picked up. The expected behaviour is only observed when NAV1 and NAV2 are the same. I say "expected" but it's misleading. For instance, set NAV1/2 to the same frequency; then verify selecting NAV SOURCE VOR1 that you can alter the course using CRS 1. As expected, compass roses in both PFDs and the CRS values in both PFDs changes. Select, instead, NAV SOURCE VOR 2. Now alter the course using CRS 1, and both compass roses, but only rght PFD CRS value will change. Using CRS 2, the left PFD CRS value will change. There seems to be a small issue here of programming variable references crossing one another, but it's so confusing that I don't want to think much about it. I suspect this might be the source of an issue I once observed during approach, whereby the PFD roses will sometimes toggle between different radials, as if the course selector is in two positions. Otherwise enjoying the heck out of this aircraft, thank you so much!