Search the Community

edit: THE SOLUTION As suggested elsewhere on this board, I had attempted starting the game in OpenGL mode by adding -force-opengl to the target field in the shortcut I use for starting the game. I had also tried the same with -force-glcore, which is the command that the warning from Textures Unlimited suggests during startup. Neither had made the warning go away, the game kept crashing, and I found a surprising affluence of "d3d" related errors in the log. THE FIX: not using the shortcut. I used the command prompt to start the game, all manual like. Been playing for over an hour now, no problems, so I'm convinced this solved the problem. Just in case anyone shares this problem, the inability to start the game in OpenGL mode, I will add a short description as the right answer. To see whether your problem resembles mine, I will leave here the whole odyssey. Starting the game in OpenGL mode was pretty much the first thing I had tried, but not knowing how to build a command into a shortcut, I had done what I had thought a description elsewhere on this message board had described. I may have gotten that wrong, though the command that had been suggested there was not quite correct, it appears, either. Regardless. If anyone loveed up, it was almost certainly me. Clumsy is a state of mind. In a previous episode: Problem: in the last few days, the game has started crashing for no apparent reason. Over the past few days, I got system freezing up or BSOD a few times. I thought updating windows and graphics drivers had remedied that. But that game just keeps on crashing. Even when it's just running in the background, after the prolonged startup my large number of mods require. Crash, while I do nothing to it. Other than the VAB, I couldn't find anything the crashes appeared to have in common. As it happened without my input, I thought "Maybe it's the Autosave!". To test this out, I went into settings.cfg and changed the long and the short intervall, by hanging many, many zeroes at the end of either. I found the game translated the entry in the settings.cfg into 3E+23 after startup. I got to play around in the VAB for about five to ten minutes. Crash. I found in the log file that Janitor's Closet was throwing many NullReference errors. So I took it out. Game still crashed. I've piled the log file, the crash dump, and all the .cfg files and such that lurk in the game directory into a zip file, hence: https://drive.google.com/open?id=1-7VGvOb9sC5uLvza72vwtRP2099HV0z9 I've also copied the addon list AVC provides me, it is hence: https://drive.google.com/open?id=1HofhzlRRj6SN_R1pHhk_yrH5BlS4EgxN Note: This list is from before I removed Janitor's Closet. While typing this, I started up the game once more, and it crashed again. This time, at the exact moment that I tried placing the base of a strut. Assemblage of log files zipped up hence: https://drive.google.com/open?id=1WlP3SKnRzwoU-0gPYF4MwOT3AbgVtLjh Then I thought "It's the VAB!" So I started up the game, told QuickStart to take me to the Space Center. It finished loading and I busied myself with something else, waiting for it to crash or not. No crash message had appeared after what felt like 20 minutes, and I thought "yay!". Then I tried moving the mouse, and the cursor was stuck. Whole system frozen up. Couldn't even get to the CTRL+ALT+Del screen, that old combo did zilch. No Crash Dump, obviously (I compared the folder names to earlier dumps I had already zipped up). The output_log, though, is here: https://drive.google.com/open?id=1zWIf2XmRDjPNecw6oqHN1XqfY6oJ50Al I would greatly appreciate any help in figuring this out. I suspect it's a mod. Actually, I'm fairly sure it's a mod. But as my wits weren't great in this to begin with, I've gone past their end a while ago. I'm presently mostly stuck at home, being chronically ill. Playing KSP is a welcome relief, so I'd really be grateful to anyone who can help me figure this out.