Skip to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/14/25 in all areas

  1. Are you using the recommended speed schedule of 290 KIAS to maybe FL270, then 270 KIAS (or IIRC M.72 above the changeover altitude)? Except for small altitude changes down low, NEVER use vertical speed mode for climbs, especially above FL200 or so. Trying to climb using vertical speed is guaranteed sooner rather than later to get you behind the power curve and result in having to descend first to get your speed back. This is absolutely real life. Happened to a couple of un-named commuter airline crews I personally know of when working as an FAA inspector.
  2. Excellent news! Very much looking forward to the update, and to a potential remake as well
  3. Hi, what is actually important for the installer is the path to the UserCfg.opt file, which right now cannot be different from what the installer is expecting for MSFS2024, by default. From this file, it will read-out the path to your community folder. The file should either be here in case of a Microsoft Store install: Or here, in case of a Steam install: You also have to install the application for the same user that MSFS2024 was installed for. Please double check where the file is located on your system.
  4. What types of approaches are they? The CRJ is not approved for certain (most?) RNAV approaches, and the FMS filters out a lot of things it considers unusable (see the pinned topic on missing airports and runways). There's something vaguely familiar about this question, like it was asked for V1 and the above was the answer. If I find the old topic I'll link it here, or if you feel like taking a dive into the past. EDIT: here it is: Perhaps the filtering has changed? Are these RNP approaches that you aren't seeing whereas GPS ones still are?
  5. OK, I seem to have fixed the problem. I don't know what caused it. I had been trying to use the 900 this whole time. So I tried the 700 and it worked, so then I tried the 1000 and it worked too. Then I went back to the 900 and now it is working as well. I don't know why it behaved that way but for now it's working as it should.
  6. I took the liberty of re-titling your post to describe the issue. That should help others add to this instead of starting new threads. Please advise if you're using any hardware devices and/or helper apps like SPAD or AxisAndOhs. And please confirm it's on a PC.
  7. Ok, I just flew another flight following this tutorial. Even though it's not for V2, I was able to reach FL330 and maintain it no problems. Now if I can just start the APU I'll be a happy simmer.
  8. I think the product page is pretty clear: As the product uses many FS2024-specific features, it would require some serious work from Jo to make it FS2020 compatible. Mathijs Kok PMDG
  9. Coupled VNAV is available as an option. I believe it was standard on the 1000 and maybe some late 900s. These aircraft will have a VNAV button, and it practically functions like VNAV you might know from Boeing or Airbus, but you have to manage thrust yourself.
  10. Afaik, the VNAV pages of the FMS contain only advisory speeds for TOD calculation. Once the white asterisk shows up on the PFD, you have to manually descend by setting vertical speed. Automatic descent does not exist in the CRJ because it has no autothrottle. See here: Chucks CRJ700ER guide Michael

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.