Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Major RNAV Approach bug in MSFS2020

Featured Replies

7 hours ago, jrw4 said:

Agreed, but that's been well established by now. But this is an LNAV only approach, so while the GP might be too steep, all that does is get me to the MDA a bit sooner. What seems odd here is that at this airport, the FMS doesn't seem to be using the ARP as the aiming point. Just something that needs to be fixed by the ATR dev......

If you're doing a dive and drive approach and there aren't any intermediate at or above constraints, then getting down to MDA earlier isn't a problem.  But if you're doing a CDFA approach (as almost all airlines operating an ATR would be), then getting down early doesn't work either.

Yeah, sounds like a definite bug for the ATR dev.  I've never used the plane but this sounds really significant; I'm pretty surprised it took this long for someone to call it out!

Andrew Crowley

  • Replies 67
  • Views 8.7k
  • Created
  • Last Reply
  • Author
15 hours ago, pmb said:

I don't have any knowledge on this topic, but there is (or better: was) a topic on CRJ updates going at the Aerosoft forum

https://forum.aerosoft.com/index.php?/topic/176550-crj-update-status-with-new-staff/

This also mentions "fixes to the LNAV and VNAV issues" by Hans.

I didn't find a contact in Hans' profile but would suggest opening a ticket with Aerosoft who may - or may not - transfer your issue report to him.

Kind regards, Michael

Thanks for the tip, Michael!

  • Author

... and they locked the thread. Again, I can't post in the MSFS forums, so I guess this will just go unaddressed.

19 minutes ago, mryan75 said:

... and they locked the thread. Again, I can't post in the MSFS forums, so I guess this will just go unaddressed.

I've noticed it. Aerosoft seems to go further and further down South. Shouldn't they be glad someone provides a detailed analysis?

Kind regards, Michael

Intel i7-13700K / AsRock Z790 / Crucial 32 GB DDR 5 / ASUS RTX 4080OC 16GB / BeQuiet ATX 1000W / WD m.2 NVMe 2TB (System) / WD m.2 NVMe 4 TB (MSFS) / WD HDD 10 TB / XTOP+Saitek hardware panel /  LG 34UM95 3440 x 1440  / HP Reverb 1 (2160x2160 per eye) / Win 11

  • Author
4 minutes ago, pmb said:

I've noticed it. Aerosoft seems to go further and further down South. Shouldn't they be glad someone provides a detailed analysis?

Kind regards, Michael

I noticed in other posts from Hans that he has a username for personal requests for support, so I just messaged him. Hopefully he sees it. Nochmal vielen dank, Michael.

  • Author

I think its systemic with the ATR, ILS approaches don't work either. I just flew the ISL 08 to SJU and would have landed in downtown San Juan had I not disconnected it and hand-flown it. I think it's VNAV in its entirety that's the problem.

So I've reached out to Hans directly, filed a Zendesk ticket with MSFS, and requested reinstatement to the MSFS forums so I can post about this there, but they will most assuredly tell me to go fly a kite. So we are where we are. Too bad, because it's a great airplane.

Time to dust off the 738!

Edited by mryan75

4 hours ago, mryan75 said:

I noticed in other posts from Hans that he has a username for personal requests for support, so I just messaged him. Hopefully he sees it. Nochmal vielen dank, Michael.

Aerosoft has always had the attitude, " if the aircraft we sell you breaks in half, you get to keep both halves". 😉

 

 

 

Archived

This topic is now archived and is closed to further replies.

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.