Game Crashing at Loading or Entering a Depot.

[AdmiralAdama]

So yeah... I hope this explains enough;

Everytime running the game, it either:

1.) Crashes during loading my saved mission

2.) Crashes (after a succesfull load) when entering a building (depot, hangar, tracking station..)

Now, at option 2, the space center is located above the sea...

Any ideas on how to fix this?

[Engineer of Stuff]

The space center is above the sea? Can I have a picture of this?

Can you give more detail? Did you install any mods before this problem?

Try running the Patcher. That *might* help.

My 200th post!

Edited December 12, 2014 by Engineer Of Stuff

[vexx32]

I'd recommend first updating your graphics card drivers. If that doesn't fix it, we'll need to see the output log as well as your settings.cfg file.

[AdmiralAdama]

Here you go....

I re-installed it; works. But then when turning it on again it gets this again and gets unable to play.

The error report states this;

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

KSP.exe caused an Access Violation (0xc0000005)

in module KSP.exe at 001b:0027bf96.

Error occurred at 2014-12-14_211622.

D:\Program Files\Kerbal Space Program\KSP.exe, run by Desley.

96% memory in use.

3328 MB physical memory [110 MB free].

0 MB paging file [2010 MB free].

2048 MB user address space [60 MB free].

Read from location 00000004 caused an access violation.

Context:

EDI: 0x00000004 ESI: 0x17117390 EAX: 0x02520dc4

EBX: 0x00e2f3cc ECX: 0x703f0028 EDX: 0x705f0028

EIP: 0x0027bf96 EBP: 0x00e2f3b4 SegCs: 0x0000001b

EFlags: 0x00210202 ESP: 0x00e2f390 SegSs: 0x00000023

Bytes at CS:EIP:

8b 1f 89 77 fc 8b 46 08 81 e3 00 00 00 c0 c1 e8

Im 100% sure it isnt the memory, because normally it works fine.

[vexx32]

Not that log file. We need the output_log.txt file. If you can't find it in the crash folder, look in KSP_Data.

[AdmiralAdama]

How to add that here as a downloadable file?

[Claw]

Drop it somewhere like mediafire, google docs, or dropbox. Then post the link here.

[AdmiralAdama]

Nevermind. 0.90.0 fixed the bug, no longer happens to me that often