Please fix this Asobo.
I hope we donāt have to wait until summer next year and SU 17 for a fix.
1 Like
Thank goodness for this post. I tried 4 flights NZAA to NZQN and reciprocal. Each timeā¦CTD. Searched google and go here. Just uninstalled the POIās, and all is well. Many thanks! Asobo, please rectify.
Just wanted to say that I had this exact issue yesterday when coming back to FS2020 after something like a year.
I happen to like flying around NZ so picked an airport near Christchurch and while it would load in, if the view changed laterally at all (either from turning the aircraft or looking to the side) the sim would instantly lock up and CTD.
I assumed it was an out of date addon so I got rid of them, when that didnāt work I tried every cache deletion and graphics edit and driver uninstall method and specific version that I could come across, and Iād pretty much given up on it. The only thing I hadnāt done was try an airport in a different region (because as I was troubleshooting I was only changing one variable at a time).
Because I have an uncontrollable fixation on broken things I thought I would trawl these forums to find out if anyone else had been complaining specifically about the sim just not working recently, and I saw this thread which blew my mind because it was my EXACT scenario.
So I jumped into the content manager and removed JUST the NZ POIs from WU12 and BAM, itās perfect.
I wish I hadnāt had to redownload the whole goshdarned sim before I found this though lol.
Iām adding my comment here because itās a bit disheartening to see this bug is 3 months old.
Seriously I had this yesterday.
This needs a hot-fix, Their Sim Update broke an existing functional area, and they still havenāt corrected it months laterā¦Ridiculous
4 Likes
Thank you!
I was turning mad looking for what was going wrong with my rig!
Flying over NZ using DX 11 rocks!
1 Like
WU 12 or WU 16?
CTD near NZCH with default C152 ā Access Violation (0xC0000005)
Hi all,
I encountered a repeatable CTD while flying the default C152 near NZCH (Christchurch). The crash occurred during āReady for flyā screen.
Crash details:
- Exception: 0xC0000005 ā Invalid Pointer Read
- Module: FlightSimulator.exe
- Instruction: FlightSimulator+0x1e6c1b9
- Read address: 0x0000000000000000
- MSFS version: 1.39.9.0
- OS: Windows 11 25H2
Context:
- Aircraft: C152 (default)
- Location: ~5ā10 NM from NZCH
- Weather: Live
- ATC: Active
- No third-party scenery or aircraft involved
Notes:
- Memory usage was stable (Commit Peak ~127 MB)
- No addons active in this session
- Crash log suggests a null pointer dereference, possibly during object update or scenery interaction
Thanks!
1 Like
Same thing here! Crashing near Nelson (NZNS). After doing 11 flights with 3 different planes(C750, A320 and SF-50) in several configuration and reinstalling POI New Zealand, I finally found this post.
The flight showing going further sout in the picture was the one without POI.
So I saw these update notes related to SU4 about bespoke airports and scenery updates. It included this section on POIs from WU12, New Zealand.
Since SU16 should be using this same āworldā and scenery now, I had a brief moment of hope that our CTD issue from this thread might now be fixed. I started up FS2020, installed a detected update (probably just an AIRAC refresh) and updated my FS2020 graphic settings to be back on DX12 (Beta) mode. I then restarted FS2020, and loaded up a flight at NZTL.
And got an almost instant CTD.
I started up FS2020 again. This time I deleted and refreshed the rolling cache, and then restarted FS2020 again for good measure.
But it was not to be. This NZ-South-Island-DirectX-12-with-POI-installed CTD is still with us. Hereās hoping it gets looked at with SU16.1.
Oh god, this thread helps a lot.
The first CTD was occured when I was doing YBCG-NZCH in a Jetstar service, it crashed when I almost got to the island. The program just mute and stuck, then back to normal for 2-3 seconds followed by a CTD. Second CTD happened when I fly form NZAA-NZCH, at the top of NZ South island.
Iām with DX12 and POI installed. Will try to disable one.
4 months passed and Asobo still canāt fix this.
let us hope for a fast update. I have disabled the POI but bcs I want to fly bushtours and
the bushtour āNew Zealand South Islandā have a dependency on this POI it was of no luck 
Tried to remove the dependency for this POI-module in the manifest but the simulator still refuse to load without the POI module loaded. So As the stubborn person I am I have gone thru the flt-file for this bushtrip and matched it with the en-US.locpak to get the coordinates and the name of the all rest of the legs I have - From the end of Leg 4 - where the CTD-s began.
Then I can still fly the rest of the bushtour exactly as it was created. I think that it was some problem also with this bushtour - and a missing airport or something - but this I have found elsewhere here in the forum and already downloaded the corrected version.
But it do not feel so good that both those problem exists and nothing seems to be done to correct it!!!
// Erland