Jump to content

Recommended Posts

Posted (edited)

Since the stable version of 2.5.2 was released I have been getting crashes, mostly on mission load (any mission, immediately after selecting an aircraft if mission configured that way). Occasionally I have also seen this crash in the editor with no apparent prompt. I have attached four sample logs from these crashes.

 

 

I have used the repair tool numerous times, and after that didn't work I have done a complete reinstall of the game which also has not helped. I have also updated my graphics drivers though they were pretty recent anyway. I have also tried loading the game with/without various modules, trying them uninstalled as well, but with no real benefits. My system has an i7 4770k, 16GB RAM and a GTX1080, with the game installed on an SSD. Any help would be appreciated; DCS is completely unplayable at the moment for me.

dcs.log-20180629-202824.zip

dcs.log-20180629-164207.zip

dcs.log-20180628-183821.zip

dcs.log-20180629-201821.zip

Edited by Decho
Posted

Whenever repair and cleanup or reinstall don't seem to help, the problem usually lies somewhere in Saved Games/DCS location (which neither repair nor reinstall affect, so the game will freeze/crash anyway). And if you say the crash happens on mission load, that sounds like a very usual occurence many of us dealt with - I'd first remove the "MissionEditor" folder from the aforementioned directory to let the game build a new one and see what happens.

 

Keep the logbook.lua file, however, as this is where your logbook and campaigns porgress is stored.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted

Thanks for the advice. I've tried that however and no joy - I purged the whole DCS saved game folder (backing up the logbook/user missions for later), and I'm still getting the crash on mission load (log file attached). Any other ideas?

dcs.log-20180630-074450.zip

Posted

The plot thickens: the open beta runs fine on one of my hard drives. As that's the same version as the stable build installed on my SSD I imagine the SSD is the thing making the difference. Any ideas what I can do about that? Have run various health checks for the SSD and everything says it's fine.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...