Project

General

Profile

Bug #18842

game crashes on VAB select

Added by konor almost 6 years ago. Updated almost 5 years ago.

Status:
Closed
Severity:
Low
Assignee:
-
Category:
Application
Target version:
-
Start date:
05/08/2018
% Done:

100%

Version:
Platform:
Windows
Expansion:
Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

After you change from SPH to VAB game crashes occasionally.
All that is required to reproduce - go to SPH, create something, leave it with name, unsaved, go to VAB, voila, crash.
Might be caused due to abundance of mods. No grudges if you set <will not fix>

error.log (34.7 KB) error.log [email protected] konor, 05/08/2018 08:21 PM
crash.dmp (236 KB) crash.dmp [email protected] konor, 05/08/2018 08:21 PM
output_log.txt (3.68 MB) output_log.txt [email protected] konor, 05/08/2018 08:21 PM
error.log (26.5 KB) error.log [email protected] JoESmash, 07/30/2018 05:09 PM
crash.dmp (634 KB) crash.dmp [email protected] JoESmash, 07/30/2018 05:09 PM
error.log (16.8 KB) error.log [email protected] JoESmash, 07/30/2018 05:11 PM
crash.dmp (212 KB) crash.dmp [email protected] JoESmash, 07/30/2018 05:11 PM

History

#1 Updated by jclovis3 almost 6 years ago

  • Status changed from New to Need More Info

I am unable to reproduce on Windows. The logs do confirm you are running mods so I would recommend you try without the mods. I noticed you were running DirectX 9. Not sure if this has anything to do with it but it wouldn't hurt to update that either after you've tried without the mods.

#2 Updated by konor almost 6 years ago

jclovis3 wrote:

I am unable to reproduce on Windows. The logs do confirm you are running mods so I would recommend you try without the mods. I noticed you were running DirectX 9. Not sure if this has anything to do with it but it wouldn't hurt to update that either after you've tried without the mods.

How do i set dx11 ?
I'm presuming the main cause of crash is Galileo Planets Modpack, or whatever it's called, happens if i change launch site from KSC to something else (in general game starts to behave oddly - onHover of buildings/objects doesn't really match the object i'm hovering over).

Do you think maybe i\you should close the ticket & post it to mod creators bug tracker ?

#3 Updated by jclovis3 almost 6 years ago

If you suspect a particular mod, remove it and try again. If that fixes it, report the problem to the developers of that mod. I can't close tickets but that is what I suggest.

#4 Updated by JoESmash almost 6 years ago

konor wrote:

After you change from SPH to VAB game crashes occasionally.
All that is required to reproduce - go to SPH, create something, leave it with name, unsaved, go to VAB, voila, crash.
Might be caused due to abundance of mods. No grudges if you set <will not fix>

I believe I may have solved this bug. I have been having VERY frequent crashes when reverting flights back to the VAB, or entering or leaving the VAB in general. I also run the Windows 64bit game and one of the only things in my error log with the crash dump is xinput1_3.dll. I'll attach my error log so you can see mine, it looks just like yours...

What I did was I went into my Windows/System32 folder and scrolled down to the xinput1_3.dll file and I renamed the file xinput1_3_fail.dll (so I could rename it back to the way it was later if I needed to for another game....NEVER delete Windows files)

Then I went into the main Kerbal Space Program folder and went into KSP_x64_Data\Plugins and copied the 32bit version of xinput1_3.dll and pasted that copy into my Windows\system32 folder. My game never crashes anymore. There is a slightly longer delay when entering the VAB now(like 5 seconds instead of 2), but my game no longer crashes.

Try that and reply here if you have any improvement. If not just delete the xinput1_3.dll copy you put in your windows\system32 file and rename the original back to xinput1_3.dll.

#5 Updated by JoESmash almost 6 years ago

I added the wrong dump and error log.....I have like 20 lol.....

#6 Updated by JoESmash almost 6 years ago

How do i set dx11 ?

You force DX11 by creating a shortcut for KSP_x64.exe. Then you right click on the shortcut and go to properties. At the end of the TARGET file path after the quotes hit space then type -force-d3d11

Then use that shortcut to launch the game. I usually send my shortcuts to the desktop.

Whenever you run mods that mess with textures like the Astronomer packs or Textures unlimited it gives that message about dx9 not being supported by those mods, but that probably isn't causing the crash. I'm willing to bet money that it is xinput1_3.dll based on your error log.

#7 Updated by JoESmash almost 6 years ago

JoESmash wrote:

konor wrote:

After you change from SPH to VAB game crashes occasionally.
All that is required to reproduce - go to SPH, create something, leave it with name, unsaved, go to VAB, voila, crash.
Might be caused due to abundance of mods. No grudges if you set <will not fix>

I believe I may have solved this bug. I have been having VERY frequent crashes when reverting flights back to the VAB, or entering or leaving the VAB in general. I also run the Windows 64bit game and one of the only things in my error log with the crash dump is xinput1_3.dll. I'll attach my error log so you can see mine, it looks just like yours...

What I did was I went into my Windows/System32 folder and scrolled down to the xinput1_3.dll file and I renamed the file xinput1_3_fail.dll (so I could rename it back to the way it was later if I needed to for another game....NEVER delete Windows files)

Then I went into the main Kerbal Space Program folder and went into KSP_x64_Data\Plugins and copied the 32bit version of xinput1_3.dll and pasted that copy into my Windows\system32 folder. My game never crashes anymore. There is a slightly longer delay when entering the VAB now(like 5 seconds instead of 2), but my game no longer crashes.

Try that and reply here if you have any improvement. If not just delete the xinput1_3.dll copy you put in your windows\system32 file and rename the original back to xinput1_3.dll.

The reverse of this also might work and is smarter. Delete/rename/move xinput1_3.dll in KSP_x64_data\plugins and replace it with a copy from your Windows\system32 folder.

#8 Updated by chris.fulton almost 5 years ago

  • Status changed from Need More Info to Resolved
  • % Done changed from 0 to 100

#9 Updated by chris.fulton almost 5 years ago

  • Status changed from Resolved to Closed

Closed in efforts of database cleanup.

Also available in: Atom PDF