There is no residual modules hanging around in the Task Manager. I’m assuming this is a Crash To Desktop (CTD). All crashes are all of a sudden the desktop appears. I tried a flight and when I clicked to select a different plane in the map it crashed. The crash point (blue bar) progressed by startup – first 50%, then 60%, then 70%, then 80%, then menu’s appeared. Any other file in the AppData folder which is required by game is always regenerated or updated by launcher during game loading in case it´s missing or updated when you change any configuration once at the main menu. The crash reports are not loaded by game at all and can be deleted manually and the “running.lock” file is deleted once you quit game normally. The only residual files created after a CTD are the crash report itself and a “running.lock” file, which is the one that triggers the “safe vs normal mode” message during the next launch. I think that´s caused by the fix they recently implemented to overcome the problem with the “checking for updates loop”, as I didn´t see that full scenery re-indexing after a CTD anytime before that fix was implemented.Ībout residual files, don´t worry. ![]() That indexing time takes ages since SU12 indeed and for some reason after some CTDs the process is repeated, leading to a complete scenery re-indexing, which can take really a lot of time. This process can even take 1 hour depending on the amount of addons you have. If any files are dated as current day/time wait till no new files are added/updated there. \AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexesĪnd short files by date. ![]() To check that launch game in normal mode, go into: From time to time we are blessed with one of those patches that generate CTDs randomly and out of nowhere and there´s no way to get rid of them until Asobo fixes the exe in the next patch.īlue bar being apparently frozen does not mean game is not loading. In particular I have suffered tons of them since AAU2 patch, like many other users, and SU13 beta, 4 Nvidia driver updates and 2 major Windows updates did not solve them yet, at least in my case, so it´s cristal clear where the problem is. If CTD happens after being at the main menu, while at world map or while flying the most probable reason then is a memory allocation error caused by the exe file itself. All content is loaded and indexed before reaching the main menu. But if it loads at least once without crashing it´s definitely not content related so don´t waste time trying to fix that content. If it crashes systematically and always at the same % of progress bar it could be a faulty content problem. I don’t use any caches in MSFS – they are all turned off (past experiences show them to be problematic and I get good performance without them). Thanks for whatever help you can provide. I have the latest Steam system and Nividia drivers installed. My last flights in MSFS were late July after 1.33.8.0 when it ran fine. of any previous residue from startup? Any suggestions on how to resolve this problem? Is there a way to “cold/clean start” MSFS – clear out all buffers/caches/etc. I am familiar with the issue of having to restart many times after a CTD to get it to fully run again, but can’t get past this one. Once it got all the way to the menus/options screen, but when I selected choose a new plane it CTD’d again, and now it won’t get past the blue bar again. I’ve restarted MSFS about 10 times, with reboots in between. ![]() On the next screen with a blue progress bar at the bottom it gets about 3/4 of the way done, and then a CTD. It asks me do I want to do a safe startup. Now I get a CTD whenever I try to start up MSFS. I was starting up MSFS when a Windows update restarted my system while MSFS was starting up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |