MSFS2020 with sim update 16 is causing CTD at the top of New Zealand’s South Island Please note, the first flight was from NZAA to NZCH, when I got to the top of the south island I got a CTD. So I tried it again with the same result. I then tried to load into NZWN, the sim loaded fine. So I tried to load into NZNS and got a CTD. Loaded into MSFS 2020 (with safe mode) and tried NZNS. Again I got a CTD. So I then started MSFS 2020 in normal mode and jumped to a bunch of airports all over NZ and Australia which all loaded fine then I tried NZKM and NZMK (both small airports at the top on South island and both times it CTD
My conclusion is that for some reason the new sim update 16 and at least my PC dont like the top on NZ south Island. Another user has a also reported this issue
Please note I did several flights yesterday over this area before the update and all was fine.
I didn’t try all the airports you mentioned, but I did load into NZKM with a flight to NZMK and didn’t have any issues. I then reversed the flight and started from NZKM going back to NZMK and didn’t have any issues. I don’t have any add-on’s on my test download, and I’m not running any sim-related outside streaming programs. I was running live traffic. I’ve got a bunch of screenshots, but they just show the takeoff and arrival airports, and some of the mountains in between them, so not much to glean there.
Sorry you’re having issues, and hope you and any others having this issue find the problem.
One thing I did notice. The second time running the sim after the initial update download and content manager updates, There were several additional updates to load. Two of them were NZMF and NZGS, neither of which is in the affected area. Can’t imagine that would affect the northern tip of south island, but who knows!
I believe I have narrowed this down to the points of interest in world update XII New Zealand. If I uninstall the points of interest I can load into a flight at NZNS however if I reinstall the points of interest I again get the CTD when loading a flight at the top of NZ south Island.
Is there a way of only loading individual points of interest so I can to try and get most of them working again? My instinct is there is a point of interest at either the top of the south island or the bottom of the north island
Same here, almost immediate CTD when starting a cold-and-dark flight at NZTL. I hadn’t even turned the engines on yet, just went into external view to look around, and then it crashed. This is definitely new behaviour as only 4 days ago I visited and flew from this exact airport in the final (1.39.9.0) SU16 beta without any problems.
Also confirming I have “World Update XII: New Zealand” installed, and I installed the pending 2.4GB update for this package that became available only after the beta closed.
The near immediate CTD now happens at NZTL in both normal and safe mode, as soon as you try to pan around either in the cockpit or external views. Event Viewer will show a simultaneous “resource exhaustion detector” event when the CTD happens.
Is there a way to uninstall just the points of interest?
I can confirm that the problem goes away if I delete the entire 12GB world update for New Zealand, but then I lose all the hand-crafted airports too, which is half the fun of flying in this region.
And of course it’s also not as much fun to fly around and explore if the POIs aren’t there. I can only assume the problem is related to the very new 2.4GB update to WU12 that was released after the beta closed, since the problem did not exist in the beta and before installing the update below.
And if that’s the case, here’s hoping they can fix this issue with another update to or rollback of the WU12 content, because an SU17 update (or even beta) is probably quite a ways off.
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report.
Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category.
If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
It will then show every subset of the WU, and you can select which installed packages you want to uninstall. Note: Mine shows “install” at the bottom right, because I’ve already previously uninstalled portions of the package and I’ve selected an uninstalled package.
I don’t know of any way to uninstall specific POI’s.
Just for future reference, when we get another WU, when you go into MP to “buy” it, you can chose “get” rather than “get and download”, and then you can go into content manager and select just the parts of the WU you want to actually install if you don’t like the whole package.
Hi FYI I reinstalled the NZ points of interest and tried a flight from NZTL. Same result as you have CTD. Uninstalled the NZ POI, The sim loaded into NZTL fine
I raised a ticket, the support team have been back in contact several time but can provide no help as the seam to feel I am the only one with this issue. It may be an Idea if you also raised a ticket
The only suggestion they can give me is to completely uninstall / reinstall MSFS. I am unsure I am prepared to do that at present as it appears to be working fine so long as I dont install the NZ POI.
Hi team. Another factor in this CTD may be your DirectX version. I was in DX12 mode when the CTD occurred. If I switch to DX11 mode, then the CTD does not happen, even with the POIs still installed. Give that a try.
I can confirm, deleting the POI’s solves the CTD. I was doing a flight from NZWN to NZQN and haflway over NZCH the sim became really stuttery, felt like a memory leak of sorts. It became so bad that I decided to close the sim. I then loaded into NZCH to see if gets worse if I am actually on the ground and sure enough the sim crashed seconds later.
Flew NZWN to NZDN in 2020 today at FL340 and didn’t get any CTD’s. I still have the original World Update NZ package installed- not the pending update that’s in the content manager.
I just had the same problem — I was arriving at NZCH from WADD, and as soon as I reached the South Island, CTD. I tried loading the aircraft in the air near NZCH, and got a CTD on the flight loading screen.
Confirmed, I just uninstalled the airports and POI package from Update XII, and there’s no CTD.
Same problem with me in New Zealand! I’ve flown south from Auckland three times now and pretty much always had a CTD in the same place. Everything after the last update! Never had any problems before that.
I was looking for a solution for always CTD at NZGT (with or without ORBX airport). Found this post and uninstalling New Zealand - Points of interest, was indeed the solution.
OMG, you guys saved me a lot of time,THANK YOU! I needed to do this tour from NZCH to NZQN for my virtual airline, and MSFS kept crashing on loading, or if I could get into the flight, still CTD before the plane reaches 3 or 4 thousand feet. Spent 2 hours disabling plugins and stuff to no avail. I knew it’s something to do with scenery or airport addons since I dealt with similar crashes before, just didn’t know which one. It could took me a couple of more hours to nail the New Zealand POI, or maybe not at all, never would suspect Asobo’s own addons.
Add another vote for the same problem; I’ll try uninstalling the POIs now. I was having trouble at NZNS. At first I thought it was a specific parking spot because I was able to load in when it switched to a different one, but then after panning around a moment, it crashed again.
