The difference is you have to stream/download the data every time you go in the same area. If the assets are heavy and you have an average connexion, you may get the same freeze every time.
Also, if everyone turns the cache off, it will put a lot more load on the Microsoft servers, which isn’t good overall and may hurt everybody in the end.
Mine one crashed every flight since update too.
After I turned off the Text-to-speech option, it seems wokring fine. Hopefully…
Forgot to mention:
Before switching off the Text-to-speech, I have also set up to show the VFR map everytime a flight start, a reinstall of the app…
Hope these helps.
I can confirm the exact same behavior with PAWS. It worked fine before 1.9.3, but now selecting that airport as the departure results in a CTD when the progress bar loading the flight gets to 85-95%. Every single time. There’s also an in-flight CTD getting too close to PAWS when it’s set as the arrival). No matter the aircraft, no matter if it’s a free-flight vs using a flight plan.
What’s more, the tiny Birchwood airport (PABV) just a little to the east of Wasilla (PAWS) behaves the exact same way.
I don’t get a lot of crashes with 1.9.3 in general. In fact many of the flights beginning at some of the big, high-detail airports load just fine. These two airports are the only 100% repeatable CTDs I’ve come across so far.
Thats the CTD´s I keep getting. Mostly on final approach or in the Smaller GA Planes just before touchdown
This man may have the solution folks, or at least an usable workaround.
I’ve had text-to-speech disabled this week because I usually play late at night and didn’t get any crashes.
From what I see, ya’ll getting crashes on descent. On discord I’ve also heard it appears to happen with airports that don’t have their own ATC which seems to tie the issue to specific ATC communication, possibly in approach to self-managed landing. Try turning text-to-speech off.
I’m gonna experiment and see if I can repro the crash with text-to-speech on and what happens with local text-to-speech.
On the other hand, of you crash when opening the VFR map, there’s already a workaround for that. Set the nav map to open at the beginning of the flight with the option in assistance → user experience and should be fine to turn one and off afterward.
Actually I got the CTD again, esp during flight that are longer than an hour. sad
Just tried Tokyo to Shizuoka (which is just over an hour) with text-to-speech set on Azure and I got a CTD on descent.
So either it’s related to text-to-speech or to something else happening during descent.
Now I’m going to try the same flight with text-to-speech set to windows local. ![]()
I just done a flight with Azure on EGLC to EDLP and it crashed on final approach. I will be trying it again with Text to Speech off and will have a look how it turns out.
Nope. Crash.
At this point, I’m starting to believe it’s simply a memory leak that makes the sim crash after approximately one hour in flight. I never crashed with flights shorter than an hour.
I’ll try a shorter flight with all on and see what happens.
Ok. I might be on to something. I did almost exactly the same flight to Shizuoka with the same arrival and approach but departed from a closer airport (Oshima) resulting in a 52-minute flight. Text to speech was set on Azure so I don’t think that matters.
The result? did descent, approach, and landing safely with no crashes.
It seems to me that the sim at the moment has a “crash countdown” at about one hour of flight. No idea what could be causing it. Memory leak perhaps?
I would advise everyone to try to keep your flights under one hour and see if it works. Also, file zendesks, the more we do, the better. I already did with my findings.
Were you flying on an a320? I checked the route, and it would take almost exactly one hour. Add the short taxi at London City and such, and if the one hour death count is accurate, you’d likely crash exactly on final.
Perhaps if you are suffering CTDs when using the VFR map, read the patch notes for 1.9.3 and you will see that there is a known issue, that OK shouldn’t be there, but relates to the use of the VFR map causing CTDs.
I’m sure that the devs will have a fix shortly, but in the meantime, maybe set your options to open the VFR map at the start of flight and just minimise it if you want to hide it.
Mine seem to crash around 30 minutes in, but I’m actually not tracking the time. As they say, “Time flies when you’re having fun,” so maybe I’ve been flying longer. I’ll check next flight and see.
How much RAM do you have?
The crashes I and others here are describing are unrelated to the VFR map. I have it set to open at the beginning of each flight and then I never really use it anyway because I fly IFR.
but the OP and others have reported CTD when using the map.
I’ve also had crashes of the type you appear to be having and if i had a solution, i’d share it.
64GB
Not having any crashes related to the VFR map.
mmmh Then it’s probably not a memory leak since I have 32.
The next time you fly, could you time it? I’d like to see how long other people fly before the sim crashes, or whether it doesn’t crash when it’s under one hour.
How long are your flights? @Abriael brought up a thought that his crashes are all less than an hour and it could be a memory leak happening at about that time. Mine are all less than an hour too, so that idea has merit.
I thought I could be having that issue too when I switched from internal to external, but I tried a bunch of different things and did a few flights where I never left the cockpit view, and it still crashed.
Interesting. Ive been rigorously testing many possibilities. Departing from the same exact origin to destination (LSZH - KMIA). So far I’m 5 hours into the flight and switched from external to cockpit several times so far no crash (knock on wood). Recent test: I opened the VFR window and detached it from the sim and I lowered the cockpit setting to Medium. So far its been fine.
I’ll update whether I complete the flight or it crashes.
I’m seeing the same thing. But I don’t think it’s a memory leak (I have 64gb). I’ve left the plane sitting on the tarmac doing nothing and still see a crash about an hour in. Sometimes. It seems if I make it an hour, I can make it 6 hours.

