I’ve done about 230 hours, not sure how many flights. Most relatively short, but several multi-hour flights. Mostly TBM 930, but some airliner and corp jet. I’ve had just a few CTDs, not enough to start counting them so I can’t be specific. Hopefully this is of some use in general.
In well over a hundred flights, I think I had one once, but I’m not even sure about that that.
My computer’s mediocre except I have 64GB of RAM. I think this has helped, especially with the suspicions of a memory leak in the sim, so maybe the CTDs are linked with that problem?
I also have a fast connection, if that’s relevant.
I’ve had one in a long multiplayer flight over Japan, where, when we arrived at Tokyo my FPS dropped to sub 20s, probably a memory leak.
Since then only once with the LED driver download from Honeycomb for the Bravo yoke. What I DO get occasionally with my new Radeon RX 6800 XT is when I click fly I end up on the runway or wherever with a FPS of around 10 FPS and the GPU at near idle, which is unflyable and takes ages to wend my way to closing down. Sometimes I have to reboot, other times I can just restart the mission in game. Probably a Radeon driver issue, as it never happened with my old nVidia1600ti nVidia card.
Only 4 in total since buying it in Sept. Not sure how many flights I’ve done. 100 perhaps. All CTDs related to mods it seems. Empty community folder = no CTD for me.
Never one here. Maybe its because I have never added anything. No add on aircraft,no scenery. Completely stock and I update when they come. I don’t plan on any add ons for a while until MSFS becomes more developed.
Absolutely none in 300+ flights.
I have and keep the 3 airliners uninstalled and use the WT mods as well as the big DA40, DA62 and VL3 mods.
I also use quite a lot of addon scenery, mostly freeware, and the Jabiru.
none, never ever.
I’d say about 1 in 6 flights.
I’ve tried many different settings and configurations and seems to not be related to anything.
It’s either within 5 minutes or after a couple hours in the air.
Never… Zero!
Like many others the only 2 crashes I’ve had were due to the VFR bugs a while back. The sim is extremely stable for me.
I think there is enough evidence for Asobo to create a crash handler which submits reports of the sim/system when a crash occurs so these can be mitigated against.
10 in 102 flights.
3 was caused by the Neo vs RAM. I realised on the 3rd crash that my RAM usage hit max. Doubled from 16gb to 32gb and that stopped happening.
4 were caused by the nav screen (v button) when that was buggy.
1 was a mod issue, I forgot to move the community folder after an update.
The rest seemingly random.
It fluctuates. Sometimes it doesn’t happen for ages, sometimes it’s 1/10, other times it’s 1/2
The three big factors for me are:
- Turned off rolling cache
- Installed on internal SSD instead of external SSD
- Switch off AI traffic
Adding removing the very few items in my community folder don’t make a difference, though I believe for some this is a factor.
Usually needs a PC reboot to stop the CTD repeating
Could be a memory issue, heating issue or just running close to the limits of the PC although in every instance of my CTDs there are no signs of my PC struggling at all, not at the absolute limits of processor, memory or GPU, so I do wonder what the true cause is. I run with moderate/medium settings. I hardly ever fly in the same place twice.
Approaches after a long VFR journey, high AI traffic, heavy ATC comms and connections to external apps seem to be common reported causes. Scenery complexity, such as cities and complex terrain don’t appear to be a factor.
My guess is that something gets triggered which causes a massive spike in memory/cpu/read/write and while most people’s PCs seem to cope fine with that, for some it causes a sudden stop. Doesn’t seem to be related to minimum system requirements as far as I have seen.
The topic seems to be very controversial/divisive, with some people complaining bitterly while others shut down any CTD complaints and blame posters as being ignorant. Probably best to accept it as a reality for some people. It doesn’t help that hasn’t been much official acknowledgement about it - maybe because it’s such a random issue.
2 CTD in 214 flights.
I am am almost 100% sure that it is hardware/power draw taken away from the computer by a space heater. Our whole-house furnace has a bad part that is on order, so the upstairs floor is without heat, currently.
Out of 120 hours of flying time, most of those 1 hour flights or less, i’ve had about 2 CTD during flight and that was back when the smart cam was causing it with live traffic and was fixed by Asobo. Haven’t had any CTD during a flight since then. Recently had a CTD on the ground using the pushback helper, which is apparently a sim connect issue with the honeycomb bravo thottles. Other than those, sim is very stable for me. Any CTD i’ve had, its been a result of a known issue. I’ve also played around with an aggressive OC on my GPU, and that caused a CTD, but thats to be expected.
I have had 3 CTDs since September, all 3 in Carenado Mooney.
0, as in zero since its release. Color me lucky I guess.
In regards to my CTDs that I have had recently, I just went to: https://outervision.com/ and I was surprised at the result it gave me using the “basic” estimated power consumption feature.
My power supply is a 1,000 watt and that website is estimating my usage, with my hardware, at: 1067W.
If you have gotten any mysterious CTDs it may be worth looking at that website to see if you have to small of a power supply. I think mine is. ![]()
Never had a CTD during a flight, but have had lots when creating missions ![]()
Nvidia just released new drivers this morning. So far much better/smoother performance for me
Almost never had a CTD unless I’ve been intentionally trying things that I knew in advance would cause a CTD.
The only time I got an unintentional CTD was once when flying really low over a large Photogrammy area for an extended period of time. I could sense my computer was straining and struggling with rendering workload before the CTD. I decided to let it keep rendering and keep flying just to see when it would break.