Check that you have BOTH hotfixes installed
CTD every flight now. Unplayable. Tried every update, tried complete fresh installs, tried everything on zendesk suggestions, don’t use mods, tried this..and that…and this…nothing works, game is broken.
ryzen 5 3600
16GB ram
3060ti
Guess I’ll wait for the next patch and hope it works, adding my specs incase it helps the devs somehow.
But you are getting in the air? Try explaining when and how and I or someone else might have an idea. Just as an example I got hit by the atc bug as I entered UK airspace but I recognised what it was and after repeating the event to test and getting the same result I simply changed a setting in traffic.
This also worked for me!
I was running Flight Simulator from an external disk formatted with exFAT, and a reformat to NTFS solved my CTD’s.
Thanks for posting!
I searched for over a week for a solution. I’m glad if it was useful to someone.
I know this wont work for everybody, but I appear to have fixed my CTD issue.
after update 5 I was experiencing CTD without error message at random intervals: when I press FLY, or in between loads, not often in flight, (although occasionally). mostly it was happening at some point in the loading process. and every time I was in game.
I tried everything on all the forums, reducing framerate and quality, turning off AI and real time air traffic, deleting community folder etc. etc
but as I was not receiving an error message, I suspected hardware.
I updated my system board bios and have been CTD free for 4 days now ( fingers crossed )
Just saying. Please make sure all your drivers and software are up to date.
Cheers
platform - PC
MSFS2020 on Steam edition
Ryzen 5900X
MSI MAG X570 tomahawk
Radeon RX6800
Corsair vengeance ddr4 3200mhz 64GB
I have used FSIM 2020 perhaps 200 times and loved the scenery and flying performance. Since the July update, I tried to fly once and got a black screen. Tried again and it said I had to install 130gb again. So I did.
I flew. It was great. Stutter was much reduced on my AMD higher end machine and I felt this was a real winner. When done I quit.
I restarted later and…FSIM 2020 starts to load and doesnt even get to the world map screen. It gets to the point where it is approximately 65% loaded, and then the monitor signal to both monitors shuts off and the computer is unresponsive (hung)… I have to pull the power cord out to get it to shut down… 100% of the time. Not even intermittent.
This issue isnt listed in the “known problems” list either as far as I could see. There are plenty of black screen issues. I tried all the solutions:
I tried:
1:emptying the community folder
2: shutting off the audio services
3: setting framerate to 30 in the nvidia control panel
4: updating to the latest nvidia drivers
5:setting the exe to administrator privileges
6: shutting down antivirus (avast)
7: defender was already shut off but turned off windows firewall
8: finally just deleted it and reinstalled the entire product from steam where I bought it.
9: reinstalled the c++ redistributable package (2017)
After ALL those things together, the behavior didnt change one bit .. Still loaded and got to about 65% then monitor signal shut off and the computer hung.
My feeling now is that Asobo has rushed an update out that is crippled…
Is there any word on when a proper update will be offered?
Fxdaddio
They better fix this crud soon as there are many unhappy customers right now.
this sounds not like a CTD , more like a BSOD and because the monitor signals gone, like a gpu issue. But as allways, hard to say. You get a log message in windows event viewer ?
There’s an official list avilable of possible incompatibilities and precautions to take but in your shoes the first thing I’d try is to unplug one of the monitors and disable any 3rd party software driving it
There is a problem with this simulator and USB peripherals for me. I have discovered that moving my Saitek Trim Wheel while the simulator is loading will cause a CTD. I have found that just before I press the ‘FLY’ button, if I toggle my trim wheel, (and all my controls) I no longer get a pause on the first use and I no longer get a CTD.
Charles.
Well to everything I already tried, you can add "convert the drive its installed on to NTFS to the list.
This is CLEARLY a crippled build from Asobo… Its AsoBAD in fact.
It’s not clear at all. Have you any overclocks hard or soft because this version of MSFS will find every one of them, possibly even your xmp settings?
I have the same core problems. I ran the sim fine for a few months, seemed to work reliably and predictably with few crashes. It was a beautiful game. Then I had to leave it for a while and when I came back it would not load. No error messages, nothing. I would start the sim, the screen goes black for a few seconds and then it would just CTD. I have tried everything, updated Windows OS (for $200), tried to uninstall the sim and reinstall, updated drivers on my graphics card, uninstalled and reinstalled C++, to name just a few things. Nothing changes. Endless CTDs. When you look through the forums on this topic the question I keep coming back to is “why can’t it just run?!?” I have played many video games in my life and I have never felt the level of frustration I feel when it comes to MSFS. Other games just play, but not MSFS. There are 40 step long troubleshooting guides to help the novice flight simmer try to get the game to run. The expense of buying a PC that can handle the graphics plus the peripherals, all the add ons in terms of software, and at the end of the day, it just will not run. I’ve honestly gotten to the point where I want to walk away from it because it is so frustrating. Maybe it is time for a less involved hobby like bomb disposal expert or neurosurgeon. Perhaps I will do a Hitler rant on Youtube about trying to MSFS to run. That might be fun. Sorry for the rant.
The CTDs seem to fall into a pattern.
-
CTDs that can be traced to a particular mod and are usually repeatable. For me using the NXi mod saw a significant increase in CTDs. As soon as I unistalled it CTDs becuase very rare. Installed it again after the NXi update, CTDs spiked. Unistalled it again, CTDs dropped off again. The creator of the NXi assures me that it only uses Javascript so could not cause a CTD. So it is likely that it triggers a scenario within MSFS (unrelated to the NXi mod itself) and then a CTD occurs. This type of CTD triggering event may also explain the CTDs in no. 2 below.
-
Random CTDs. These CTDs seem to occur at random times, with random aircraft, in random locations, with or without mods. There is simply no way to identify when they might occur, and they are not repeatable. Could be loading MSFS, or loading a flight, or during a flight, or even when returning to the main menu after a flight. For me they are rare, but only started after SU5 hotifx 2. Which is funny really, since that was supposed to address CTDs.
-
Hardware related CTDs, overheating, overclocking etc. I would have thought that these types of CTDs would not be influenced much by MSFS updates. As SU5 reduced system resources, theoretically we should see fewer of these CTDs since the system load is lower. I would have thought that these types of problems would see Windows fail rather than just MSFS.
Unfortunately all this points to MSFS itself being the culprit in the majority of CTDs. There would seem to be a need for MSFS to have some sort of “unexpected error” handling built in. Either so that it just ignores scenarios it can’t handle or spits out some sort of report that advises what event it encountered that it couldn’t handle.
I miss the MSFS of months ago. Sad.
Agree, but if I went back I would miss the performance improvements I now have. The grass is always greener on the other side.
The people are crazy about FlyByWire, jesus.
You need to lookup “Direct Storage”, because at a guess the boost many of us are getting is because of this better data handing and the new imbalances are going to upset many an overclock, possibly including XMP profiles.
Unclocking is on Asobo’s list
My CTD’s were resolved in an inexplicable way. Today I was able to install the current nVidia driver (version 471.68, game ready) and some Windows updates and as a trial I made a one-hour flight from Amsterdam to London in a modified Cessna Citation Longitude, and that without crashes!
Installed addons were:
- Flightsim.to “Cessna Citation Longitude Improvement Mod”
- “Working Title G3000” and “Working Title G3000 Roaddata” Mod
I also click the “repair”-button in the app-settings:
type “Microsoft Flight Simulator” in the searchbar → right click → app-settings → scroll down and hit repair
Addendum: I also deleted all content in the Temp folder. This can be found under: C: \ User \ xxxx \ AppData \ Local
I can finally fly again. Unfortunately, the graphics, the photogrammetry (!!!) in the most big cities and the LOD are still not as nice as they were before the Sim update 5. On the other hand, the game runs much more smoothly and with fewer micro-stuttering.
Please keep this game up to date Asobo!
One day later:
I was happy too soon. I was just about to fly another lap from Innsbruck over Mont Blanc to Nice. Less than 30 seconds on the world map and I have a CTD. The game is still unplayable.