Game crashes after load

[Lillz]

Hey. I have more than a few mods installed, but not a ton either. The game was working fine earlier today and now it crashes after loading.... not sure what it is... someone know what's going on?

Error.log

part of output_log

I think I may be out of memory for the game (even though my system has 16gb) because 64bit works but crashes when entering VAB

[Guest]

line 121 of output log :

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

And this is not the only time out of memory shows up. If you want to run the texture replacing stuff like city lights etc., you are going to have to take steps to ensure that you have enough memory available. I don't care if your system has 2Gb ram or seventy billion, KSP can only allocate a little less than 4. I run the game on less than 2Gb ram, but I also make sure nothing is running in the background, like anti-virus, and I don't leave anything else, like web browsers, open either. ATM(http://forum.kerbalspaceprogram.com/threads/59005-0-25-Release-3-8-Oct-16-2014-Active-Texture-Management-Save-RAM!) can work wonders when it comes to running the texture mods on the 32 bit client.

Patience is required more than anything, and considering you've been around since the forum crash of 2013 and have a total of 10 posts, I believe you have patience. I have confidence that Unity and Squad will eventually get the 64 bit client ironed out and working. In the mean time, running KSP on Linux may be worth your time to investigate and try.

Edited October 31, 2014 by Otis

[slumpie]

Try "-force-opengl"

[skeevy]

Your only options are lowering graphics settings, running with opengl, and using Active Texture Management; well, and switching to 64 bit KSP on Linux. Other than that, all you can really do is hope Squad either fixes the current Windows 64bit version or moves to Unity 5 and hope that 64bit works better with it.

[Lillz]

line 121 of output log :

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

And this is not the only time out of memory shows up. If you want to run the texture replacing stuff like city lights etc., you are going to have to take steps to ensure that you have enough memory available. I don't care if your system has 2Gb ram or seventy billion, KSP can only allocate a little less than 4. I run the game on less than 2Gb ram, but I also make sure nothing is running in the background, like anti-virus, and I don't leave anything else, like web browsers, open either. ATM(http://forum.kerbalspaceprogram.com/threads/59005-0-25-Release-3-8-Oct-16-2014-Active-Texture-Management-Save-RAM!) can work wonders when it comes to running the texture mods on the 32 bit client.

Patience is required more than anything, and considering you've been around since the forum crash of 2013 and have a total of 10 posts, I believe you have patience. I have confidence that Unity and Squad will eventually get the 64 bit client ironed out and working. In the mean time, running KSP on Linux may be worth your time to investigate and try.

Ahh yes I thought I remembered there was a texture management thing -- just couldn't remember the name. Yeah, I've been around here before 2013, my stuff just got erased after the crash. I think the first build of KSP I played was when eve and the other planets were introduced... 0.16 right? Such a long way it's come and there's people here that have been around since build 1. Fantastic community.

edit: Before trying texture compression, I tried Opengl. It works very well and in the time I've been playing, I would have crashed multiple times... OpenGL rules!

Edited October 31, 2014 by Lillz