Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
- This is using any plane in career, even when using the 172
- 10% of the time it is when you line up and increase throttle to take off
- 90% of the time it is when you configure for landing at the destination
- Recently I unlocked certificates that enabled live weather, but the increase from 1 in 5 to 9 in 10 CTD's feels like it happened a few days later.
- Game also hangs 99/100 times when closing. It minimizes and the desktop is visible, but the game still runs, and I have to use steam to forcefully quit the process.
The only Cesna 172 whitch doesnt crash the game is the cargo version.
I see that i have another Cesna 172 link to the career ?
Anyway, I decided to delete the rolling cache file:
C:\Users\YOUR_USERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\ROLLINGCACHE.CCC
I assumed the game might have sabotaged itself, as the problems seemed to get worse over time. Deleting the rolling cache seemed logical since it may have accumulated some errors over time. And lo and behold, after deleting it, the game created a fresh cache file and repopulated it.
Since then, I have successfully completed two consecutive flights in a single session without any crashes. So, fingers crossed! But this might have been a case of a self-sabotaged rolling cache by the game.
I did a fresh reinstall (all settings were kept), deleted rolling cache and created it again. Since then ok.
So since I already verified the game files, I did not do a full re-install. I just wiped the rolling cache file only. Via Windows. While the game was not running. And so I kept all other files and settings. I just deleted the one file only:
C:\Users\YOUR_USERNAME\AppData\Roaming\Microsoft Flight Simulator 2024\ROLLINGCACHE.CCC
Perhaps this is a (temporary) fix for others too, if they run into this, until Microsoft patches some more next year. At least now, we can perhaps somewhat get around the dead-end this was, and play the game over the holidays, despite the other bugs in there.
Thanks for confirming Patpat!
So, since it worked for me yesterday, I'm thinking its either one of two things:
1. This might still be a server-side issue, not a rolling cache issue. Maybe I was lucky.
2. Or, what did I do differently yesterday when it worked?
So, I deleted the rolling cache again, started the game again, and then I did what I did yesterday: the first flight in a Cessna 172, a short ferry flight.
Yesterday, I did it just as a small test, but today, I'm starting to think it matters. After deleting the rolling cache again following today's game crash, I did a Cessna 172 ferry flight first, and that worked. And within the same session, I did some other flights too.
It almost seems like some of the stuff the game needs, and other planes need, are included with the Cessna 172 only. Perhaps something like the G1000 Garmin stuff. Even the broken PC-12 can be somewhat flown after using the Cessna first, using the same AP button binds.
Anyway, this was all before patch 1.2.8.0. I haven’t tested patch 1.2.8.0 yet, which claims to have fixed some game crashes. To be honest, it's all still Russian roulette. What a shame.
edit: nvm I see "no overclocking". I'd still check your event logs to see what is going on before the application hang. You may need to use DDU(Display Driver Uninstaller) to completely wipe your driver and registries in safe mode and install the latest AMD driver for your GPU.
But before my AMD GPU driver update it froze and the computer required a full reset. Now its a CTD, and when it does, it ends with a AMD message offering to send a report to AMD. So it looks like a GPU crash.
I am just not sure why. Since it is very random. Sometimes it works well for a few hours. Others, it crashes a lot. And it is only MSFS2024 that does that. All other apps, even very demanding apps, do perfectly fine all the time.
Maybe it's some (AMD related) VRAM memory leak? Whatever it is, it is frustrating.
Today I am going to test out 1.2.8.0 and see what happens. Wish me luck.