Saffa_Jake812

I think one of the main reasons is that Totoriko only programs and tests in Linux and needs that capability before MFS will even be considered.

This is where the true state of the sim is revealed, the good and bad.

Yes, using two monitors and in an attempt to follow along in the video I realised you are popping out the chaseplane window. I tried the same and my sim crashed when I do that. I have actually never been able to pop out windows on my sim without a crash.

I do not see this issue with the same add-ons and the setup is also the same, with one exception - I run the sim in full screen rather than windowed. Could that be the issue?

Try deleting your UserCfg.opt file and boot the sim. The file will be recreated by the sim but you will need to set your graphics settings the way you prefer it. This worked for me last week.

Update: This issue has now been logged as a bug by the mods over at the MFS forums: https://forums.flightsimulator.com/t/su16-reproducible-ctd-over-nz-south-island-with-nz-pois-and-dx12/732728/25

Are you running DX11 and do you have the Nvidia App installed? If yes to both then that might be the issue.

I can confirm on my end that booting into the sim with DX11 instead of DX12 also resolves the CTD issue over NZ.

Regarding the DX12 without frame gen suggestion, that does not work for me and I still see a CTD. I have also cleared my SceneryIndexes but that does not resolve it either.

Here is the TLDR: PMDG cannot reproduce this and therefore are unable to fix it for now.

Just a note that over at the official forums it appears that this issue is also related to DX12 for some strange reason. Unfortunately my sim does not want to boot with DX11 so I can't test this.

You are most likely experiencing what is described here: https://forum.pmdg.com/forum/microsoft-flight-simulator-2020-2024-products-discussion/pmdg-777/general-discussion-aa/355337-777-200er-in-msfs-2020-periodic-stutter/page3 There are two workarounds: keep the W&B page open on the EFB during your flight or delete the W&B page code from the EFB file (PMDGTablet.js)

I do not believe there is any use to do that as commenting out the file or deleting the entire POI pack has the same result with no POI shown. For now it is no POIs if you want to fly over the South Island of NZ until MS acknowledges the issue and fix it, of which no one knows the timing for that. The other option is if there is someone out there who have not updated their NZ POIs and they can share the files or create a community folder version.

Looks like the culprit is this file: OneStore\microsoft-newzealand-point-of-interest\scenery\Microsoft\newzealand-pois\objects.bgl Commenting it out in the layout.json file also stops the CTD from occurring but it looks like POIs do not load.

Yep did it three times all CTD. Did it once without NZ POIs and no CTDs at all for the 15min in the air.