Hello,
Since Sim Update 16 (SU16), I have been experiencing constant CTDs (Crashes to Desktop) when flying long-haul flights. The crashes occur after 5-6 hours of flying without any error messages or warnings. The last CTD I had in MSFS 2020 was about two years ago.
Before SU16, the sim was perfectly stable, and I was able to complete multiple long-haul flights lasting over 10 hours without any issues. Now, it’s impossible to complete a long-haul flight, no matter which aircraft I use—be it the PMDG 777, iniBuilds A350, or TFDI MD-11. I haven’t installed any new mods or addons since updating to SU16.
Maybe someone is experiencing something similar? The routes on which I have CTDs were, for example, EDDF - ZUUU (default scenery), OMDB - RJAA (RJAA from Drzewiecki), and LFPG - FMMI (default scenery).
Can’t say I’ve experienced the same, I fly long hauls exclusively in the 789 up to 15-16 hours, no CTD as of yet.
Thanks, are you flying on MSFS2020 also over Asia region?
Flying 2020 on steam and yes flying from North America to Europe / Asia.
I’m getting the same thing happening after SU16 (at this point, can the please just leave MSFS2020 alone!). Long-haul flights I get a CTD 2-6 hours into flights. It’s happened with PMDG 777-300ER in Asia and Headwind A339 North-East Europe. MSFS2020 had been rock solid for me for a year now.
Faulting application name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000268824
Faulting process id: 0x183C
Faulting application start time: 0x1DC185B8EB2B71B
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 4c105a19-3ba4-4efe-a26c-5d724bc5036b
Faulting package full name:
Faulting package-relative application ID:
1 Like
If you have FSLTL running it may be related to that navdata bug in Asia that’s causing ctds.
2 Likes
Thanks for the advice. I was running FSLTL both flights. I’ll try without it.
Hello,
I performed some intense testing and it seems that the issue with CTD (Crash to Desktop) occurs when flying in an eastbound direction. Whenever I have flown from west to east (it doesn’t matter if it was from Europe, North America, etc.), the CTD occurred. It looks to me like there are some bugs with the navdata in MSFS. I spoke about this on another forum, and a member (my colleague) told me that this kind of issue had already been present in MSFS but was fixed in an earlier Sim Update. Microsoft/Asobo probably somehow reproduced this issue in Sim Update 16.
1 Like
Hi, thanks for this info. Do you have more info about this?
Hi all! This is very interesting, I just came back home and got a CTD. I was flying long haul too from Munich to Hong Kong. IniBuilds a359 and it CTD’d over China Region. This has been happening ever since the new sim update. Flying from Sao Paulo to Doha (16Hrs) was no problem (also SU16) a couple days ago. I thought it might have been the VHHH WF scenery but it’s not. I used to get CTD’s that showed that <msvcp140.dll> was missing so I just installed it again. Now it shows me the error mention from the original post. Very weird, I hope they fix this. I have navigraph updated if that matters…. Hope someone can find a solution!
I also had this issue, sadly no fix yet. I did fly ZSPD-PANC using AIG traffic, seemed ok but needs more testing to see if this is a alternative.
Interesting…. I just had a CTD again. Hong Kong to Shanghai, so around China region I keep on getting CTD’s……
CTDs after SU16 are caused by traffic injectors, no matter which one you use. In SU16, MS/Asobo completely broke the navdata that injectors use. There are two topics in the bug reporting section about this: - FSLTL Crashes - Fix - Bug Reporting Hub / Crashes (CTDs) - Microsoft Flight Simulator Forums and CTD with AI Traffic enabled (FSTL) - Bug Reporting Hub / Crashes (CTDs) - Microsoft Flight Simulator Forums. A potential solution for now is to stop using traffic injectors and AI traffic. I’m testing this now to see if it helps. Please also upvote those topics.
1 Like
I used AIG Traffic Controller yesterday out of ZSPD and it seemed ok but need to test further
It is completely random when a crash to desktop (CTD) can happen. Based on an investigation through different forums and Discord servers, the most prominent area for this seems to be Asia.
Me too, I have most CTDs when flying to Hong Kong or anywhere in Asian region. And it only happens when using FSLTL… it’s really annoying
1 Like
I will try AIG more and report back with my findings to see if it is any more stable than FSLTL.
I’d love for anyone to point out what has actually been updated in SU16
Should be called SD16 sim downgrade 16. LOD issues, CTD’s, bad nav data, satellite imagery downgrade and the rest. Hopefully MSFS can sort it out, not all of us have an internet connection suitable for MSFS24, or have a desire to switch to it. SU15 worked just fine.
2 Likes
I am using FSLTL indeed but how could I fly without any problems with AI enabled from SBGR to OTHH? I don’t understand sometimes…
I think it just depends on which airport or region’s data is broken. I also flew some long hauls, like EDDF - KLAX or KATL - SAEZ, and had no CTDs. The bad news is, in my opinion, it’ll take a long time until Asobo/MS fixes this.
