(SOLVED)Crash when loading

[martyns1234]

(SOLVED)So i'm not an expert at programming, so could you help?

output log

Spoiler

https://paste.ee/p/YbRyU

error log 

Spoiler

https://paste.ee/p/lPdNx

 

Edited August 16, 2018 by martyns1234
SOLVED

[4x4cheesecake]

Welcome to the forum

I cannot find anything interesting in your log except for this:

Quote

93% memory in use.
8103 MB physical memory [522 MB free].
11173 MB paging file [106 MB free]

Well...technicall,y there is some RAM left but my best guess is: You run out of memory. Remove a few mods (I guess OPM & GPP will use a lot of RAM) and try again.

Edited August 14, 2018 by 4x4cheesecake

[martyns1234]

9 hours ago, 4x4cheesecake said:

Welcome to the forum

I cannot find anything interesting in your log except for this:

Well...technicall,y there is some RAM left but my best guess is: You run out of memory. Remove a few mods (I guess OPM & GPP will use a lot of RAM) and try again.

i don't use gpp or opm

Edited August 15, 2018 by martyns1234

[Xd the great]

1 hour ago, martyns1234 said:

i don't use gpp or opm

Remove other mods?

Or closing background apps.

[4x4cheesecake]

8 hours ago, martyns1234 said:

i don't use gpp or opm

The linked log tells a different storry (check line 565 and 571):

Quote

Folders and files in GameData:
[...]
GameData
GPP
[...]
Kopernicus
ModularFlightIntegrator
OPM
OPM_FinalFrontier

I just noticed the GameData folder but if you don't use GPP or OPM, this is the wrong log anyway...

[martyns1234]

1 hour ago, 4x4cheesecake said:

The linked log tells a different storry (check line 565 and 571):

I just noticed the GameData folder but if you don't use GPP or OPM, this is the wrong log anyway...

• no dude, its the right one
• when the error popped up i clicked go to the crash location or something like that. 

[4x4cheesecake]

1 hour ago, martyns1234 said:

• no dude, its the right one
• when the error popped up i clicked go to the crash location or something like that. 

The error log might be the right one and I stick with my first guess, that you probably run out of memory.
But your output_log ist definitly not the correct one and I just found another clue for this:

Your error log says, you play on KSP 1.4.+:

Quote

Kerbal Space Program [version: Unity 2017.1.3p1 (02d73f71d3bd)]

But your output_log says, you play on KSP 1.3.1:

Quote

Initialize engine version: 5.4.0p4 (b15b5ae035b7)

[...]

[KSP Version]: 1.3.1.1891

The location of the logfiles changes during these KSP versions, the output_log for KSP 1.4.+ is  located in ' %USERPROFILE%\AppData\LocalLow\Squad\Kerbal Space Program\output_log.txt '

If you can upload the correct output_log, we might find another possible reason for your game crashing

[martyns1234]

ok ill set the output log up, but now it just stuck on module manager or something like that

 

this one ? 

Spoiler

https://paste.ee/p/wmAnf

 

[4x4cheesecake]

3 hours ago, martyns1234 said:

this one ? 

  Hide contents

https://paste.ee/p/wmAnf

 

This one looks better

I was hoping for some exceptions but there is not a single one in your log. Usually, this is a good thing, but that's unexpected for a crashing game...especially since you got ToolbarControler and HangarExtender installed and both mods require 'ClickThroughBlocker' but still no exception (both mods are bundled with interstellar, maybe they modified them...or the game crashes before these mods are loaded...I don't know)

Your log just stops while the game is loading some KSPedia articles, so you can still try to install ClickThroughBlocker but without an exception, I highly doubt it is the reason for your issue.

Can you do me a favor and verify, that the log is complete? Just scroll to the end of your local file and the file you have posted at pastebin and check if they end at the same position. Pastebin got some restrictions regarding the filesize and I just want to be sure that the log is complete.

[Lisias]

On 8/14/2018 at 1:24 PM, martyns1234 said:

So i'm not an expert at programming, so could you help?

error log 

  Hide contents

https://paste.ee/p/lPdNx

 

The X_Input is involveed on the crash log. There's a good chance that this thread can help you:
 

@Just Jim, I think this may interest you.

[martyns1234]

thx

Spoiler

 

[JoE Smash]

@martyns1234, how did you solve the crashing?

By messing with xinput1_3.dll?