peak82

Hey there, just wanted to report that this issue still persists many months later. It seems that the airport doesn’t play nice with “heavier” aircraft addons. Has anyone looked into this? It’s too bad that I’ve hardly used this airport since it doesn’t work with my primary aircraft.

Forgot to mention this: uninstalling Asobo’s Texas City Update has no affect on this issue’s persistence.

I experience a CTD most of the time I try to start a flight with the PMDG 737 on Xbox Series X. If I manage to not CTD, the black avionics bug will still occur, making it impossible to start my flight. Same thing happens on landing at KSAT, guaranteed black avionics. The airport is completely unusable with that aircraft. Same thing *doesn’t* happen at your KDTW (a much larger and more detailed airport) so I’d bet a bit more LOD is needed to make this airport usable with the more advanced aircraft.

CTD occurs 100% of the time within 2-3 minutes of launching a flight at KBUF. Often, MSFS crashes as soon as I click "Fly Now!". The CTD still occurs even if I control for other potential contributing factors; I have tried to launch the flight with HDR off, air traffic off, airport ground traffic off, and without any potentially conflicting addons. This problem is not unique to your addon. It seems that many other "heavy" addons seem to cause the same CTD. Even Asobo's KDFW and LSZH (which are not third-party) cause the same CTD 100% of the time on the Xbox Series X. The CTD seems to be the result of a memory leak within the sim itself, and therefore it must be addressed by Asobo. However, until Asobo fixes this memory leak, I'd strongly suggest that the details/weight of this addon are dialed back for the Xbox Series X since it is currently completely unusable. If that isn't possible, is there any other way to prevent the CTD?