PSA - If you are having trouble with consistent CTD's in MSFS 2024, try deleting / rebuilding your rolling cache

[D Dragon]

I was having a pretty rough time with MSFS 2024 SU3 beta over the last few weeks struggling to figure out why I was constantly experiencing poor framerates and CTDs every time I got to the approach phase of my flights... at first I thought it was related to some WASM issue with the A350, but soon found that it occurred regardless of the plane I was flying. I tried correlating the behavior to 3rd party tools like BATC, GSX, Navigraph, etc, but regardless of what I disabled I was still experiencing crashes. I was almost ready to give up on SU3, but after updating my video driver (Nvidia), and deleting / rebuilding my rolling cache file, the CTDs ceased, and as a bonus everything, including the A350, is running markedly better. At least on my system now the A350 is absolutely lovely to fly. I know this is not a guaranteed fix for all CTD issues, but at least in my case it was definitely the cure.

[haza2]

5 hours ago, D Dragon said:

I was having a pretty rough time with MSFS 2024 SU3 beta over the last few weeks struggling to figure out why I was constantly experiencing poor framerates and CTDs every time I got to the approach phase of my flights... at first I thought it was related to some WASM issue with the A350, but soon found that it occurred regardless of the plane I was flying. I tried correlating the behavior to 3rd party tools like BATC, GSX, Navigraph, etc, but regardless of what I disabled I was still experiencing crashes. I was almost ready to give up on SU3, but after updating my video driver (Nvidia), and deleting / rebuilding my rolling cache file, the CTDs ceased, and as a bonus everything, including the A350, is running markedly better. At least on my system now the A350 is absolutely lovely to fly. I know this is not a guaranteed fix for all CTD issues, but at least in my case it was definitely the cure.

That's great feedback, thank you very much. 

 

[Farlis]

Yeah that's one of those things:

I noticed these issues back in MS2020 with the rolling cache and therefore never used it.

When they announced that the rolling cache would be mandatory for MS2024 I foolishly assumed they had ironed out those issues because you now can't escape using it.

Turns out they did not.

So be sure to do this regularly, as counterintuitive as it may seem.