Selecting KSEA causes CTD (2501.1)

Navigation Data General MSFS Data
1

Good Morning Folks,

This report is for FS-2020. Notably MS just pushed their AIRAC out, so my version does have that cycle present.

I just ran a clean vs. NG AIRAC test, and indeed - selecting KSEA at the World Map causes a CTD. I have a clip if you’d like to see it. It’s sort of unclear at the end, but I definitely crashed out. Discourse let me upload it, so here it is. At the end where you see all the cursors flying, - I already CTD’d at that point.

I did remove NG and retested. Standard AIRAC is okay.

Please let me know what else you need. I’ll send some users over here to validate as they raised it originally in the Official Forums.

Thanks!

2 Likes
2

Yeah, I reported this in another similar thread…

It’s not just selecting/zooming in to KSEA. I selected KPDX, and at that zoom level, started panning north in the map. Just past Ft Lewis, the sim crashed while in map mode.

It’s something in the 2501.1 that’s causing the crash.

3

I’m having the same issue at KSEA. Flew in there fine yesterday, but selecting it as a departure today, I get CTD every time. Loaded the new AIRAC after I landed at KSEA yesterday. Thanks. Ian

4

I am having the same issue in Chicago

5

Same CTD issues in the Northeast US.

6

Navdata Folder is conflicting with KSEA, when taken out of community folder sim loads, when in folder sim crashes when loading to KSEA. This happens with default and paid version of KSEA.

8

I am having the same issue at KSEA for MSFS2020. If I uninstall the navigraph AIRAC no crashes. If I reinstall it, crashes. I also tried just have navigraph and no other mods running. Still get a crash at KSEA. Started happening when the MSFS2020 ARAC installed.

9

For me too, KSEA instant CTD when zooming in on map.

10

MSFS2020.

Definitely an issue in the Seattle area. With the new AIRAC removed, no problem.

With the new AIRAC installed, I zoomed in to PDX airport level, and started panning north. No problem until just north of Ft. Lewis when the sim CTD.

Edit: I’d also recommend a future ability of the Hub to allow to rollback to the previous AIRAC version to mitigate issues like this in the future.

11

Same issue it the Seattle (KSEA) area. Should I open another support thread?

12

I’m also seeing the same issue at KSEA

1 Like
13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

15

Same issue here in msfs2020 when you select KSEA as departure and zoom it automatically. Simulator are up to date as well as navigraph. Any fix? Thanks

16

I am having this problem as well. Whenever I zoom into KSEA, the world map in MSFS2020 briefly freezes and then CTD. I removed ‘navigraph-navdata-base’ and ‘navigraph-navdata’ from the community folder and was then able to zoom into KSEA without any issue. After reintroducing the Navigraph folders back into the community folder in MSFS, I was able to zoom into a sample of other US airports without issue, but KSEA again led to a crash.

17

We are working since the weekend on a fix, but first, we must understand why this happened at KSEA. I can also confirm this CTD precisely as you all have described.

Thanks to all for your help. We will inform you when it’s fixed and we have released a new revision.

Cheers
Richard

1 Like
18

table td { border-collapse: collapse; } body[dir=rtl] .directional_text_wrapper { direction: rtl; unicode-bidi: embed; } @media only screen and (max-width: 768px) { .simplified-email-footer .namecard { display: block; min-width: 100%; padding: 0 0 16px 0; } .simplified-email-footer .content { padding: 16px; } }

KBLI as well, I narrowed it down to the Navdata base file.
When that file is removed I get access to KSEA.
This affects MSFS2020, MSFS2024 is working.
Put last months data back in & KSEA doesn’t crash the Sim. NiFly

19

Guys,
First, thank you very much for your patience and hints in the last couple of days. Much appreciated …

We worked hard over the weekend to identify and solve the issue. I have built revision 2, which is available now via the Navigraph Hub. Please update your current cycle 2501 with this revision for MSFS 2020.

We have done a lot of tests now, and it looks good to us that this issue is solved now. Any feedback is welcome :wink:

Cheers,
Richard

4 Likes
20

Thanks so much! All working here. Just did a flight where previously it would crash (at 7B2, for the record.)

1 Like
21

As always, a fast and efficient turnaround. Thanks Richard and the Navigraph Team!

1 Like
22

I am still seeing the same issue when trying to load into Chicago, it happens usually with in I’d say 30 seconds of spawning at an airport there. So before I can click ready to fly. Same as this post: