KSP (32 bit) Freezing all the time after .90 update

[Tohkur]

So basically I can't get into a game since it was updated to 0.90.0.705. KSP keeps freezing on me at random times. Sometimes it will load into the game and when I click on any building it will just freeze. sometimes I can build in the VAB or SPH for a few sec/min and then it will freeze (still can hear the background audio.) Other times it won't even get that far; I will try to load a new game and I will hear the birds in the background, but the scene wont change to the space center. The game isn't crashing (no crash info in either log) but just freezing on me.

It does this after 6+ "clean installs" (deleting local content from steam and the remaining files in windows explorer) on both modded and unmodded copies. I even installed it (unmodded) to 3 different HDD's to be sure it was a clean install; freezes still occur.

Memory usage for KSP never goes above 1.9 GB; however most of my RAM is "cached" as opposed to "free" (not that that should make a bit of difference in win7.)

What is really confusing me is that it is doing the same thing on both modded and unmodded installs with new save games, which is telling me that there is something wrong with the game itself, and not the mods I have (which all worked flawlessly prior to .90) or because of the killed/fired Kerbal bug.

System is FX-6300 (O.C. to 4.5GHz on Corsair H80i,) 16 GB Corsair Vengeance Ram (2x8GB Kit Tested OK with Memtest86 v6.0 and Windows Memory Diagnostic Tool), GTX 770 2GB driver version 347.52, Win 7 Pro 64bit, KSP version 0.90.0.705 (all mods updated to .90 compatible when running modded install), Steam version: 1424305157

After this many uninstalls / re-installs / moving the game dir / no mods / lots of mods + active texture manager, with the game freezing every time no matter what I do... I am at a loss... Any Ideas?

[All other games (including Star Citizen) are working fine]

Output log (unmoded):

https://drive.google.com/file/d/0B7U2eHh0eg4BaEZCdTFrbkdPbjA/view?usp=sharing

KSP log (unmodded):

https://drive.google.com/file/d/0B7U2eHh0eg4BU0tCMmhnTTJQZkU/view?usp=sharing

KSP memory usage:

https://drive.google.com/file/d/0B7U2eHh0eg4BZGFGZWlleUNsSlU/view?usp=sharing

System memory usage:

https://drive.google.com/file/d/0B7U2eHh0eg4BS0MzZDN4YUpzdkk/view?usp=sharing

KSP buildID:

https://drive.google.com/file/d/0B7U2eHh0eg4BZmQ2LUtyc3lCYnc/view?usp=sharing

[johnjeb]

So basically I can't get into a game since it was updated to 0.90.0.705. KSP keeps freezing on me at random times. Sometimes it will load into the game and when I click on any building it will just freeze. sometimes I can build in the VAB or SPH for a few sec/min and then it will freeze (still can hear the background audio.) Other times it won't even get that far; I will try to load a new game and I will hear the birds in the background, but the scene wont change to the space center. The game isn't crashing (no crash info in either log) but just freezing on me.

It does this after 6+ "clean installs" (deleting local content from steam and the remaining files in windows explorer) on both modded and unmodded copies. I even installed it (unmodded) to 3 different HDD's to be sure it was a clean install; freezes still occur.

Memory usage for KSP never goes above 1.9 GB; however most of my RAM is "cached" as opposed to "free" (not that that should make a bit of difference in win7.)

What is really confusing me is that it is doing the same thing on both modded and unmodded installs with new save games, which is telling me that there is something wrong with the game itself, and not the mods I have (which all worked flawlessly prior to .90) or because of the killed/fired Kerbal bug.

System is FX-6300 (O.C. to 4.5GHz on Corsair H80i,) 16 GB Corsair Vengeance Ram (2x8GB Kit Tested OK with Memtest86 v6.0 and Windows Memory Diagnostic Tool), GTX 770 2GB driver version 347.52, Win 7 Pro 64bit, KSP version 0.90.0.705 (all mods updated to .90 compatible when running modded install), Steam version: 1424305157

After this many uninstalls / re-installs / moving the game dir / no mods / lots of mods + active texture manager, with the game freezing every time no matter what I do... I am at a loss... Any Ideas?

[All other games (including Star Citizen) are working fine]

Output log (unmoded):

https://drive.google.com/file/d/0B7U2eHh0eg4BaEZCdTFrbkdPbjA/view?usp=sharing

KSP log (unmodded):

https://drive.google.com/file/d/0B7U2eHh0eg4BU0tCMmhnTTJQZkU/view?usp=sharing

KSP memory usage:

https://drive.google.com/file/d/0B7U2eHh0eg4BZGFGZWlleUNsSlU/view?usp=sharing

System memory usage:

https://drive.google.com/file/d/0B7U2eHh0eg4BS0MzZDN4YUpzdkk/view?usp=sharing

KSP buildID:

https://drive.google.com/file/d/0B7U2eHh0eg4BZmQ2LUtyc3lCYnc/view?usp=sharing

I have experienced similar, since the last update the game failed on revert to launch or hangar, after 5 steam removals and kerbal reinstalls and days of some people attempting to help but others just flaming me, as it works on their system, I have concluded the same, the game is broke. hope you have more luck than i did getting it going. Sad that on a machine that runs wow fine at good settings and civ 6 at max wo issue, Kerbal is failing. So 0.90 is broken in someway if so many peoples games have started crashing.

[Tohkur]

Update:

-force-opengl = lots of graphical glitches for me (only bottom left quadrant visible)

RAM checks out (Memtest86 v6.0; 6 passes, windows memory diagnostic) with 0 errors

Tried the fix for freezing from fired/dead kerbal bug; no luck, still freezing (no entry in persistent.sfs for rescuing any kerbal, stock patch did nothing)

Rolled back video drivers to 770 disc original; no luck, still freezing

Reinstalled 347.52 video driver; no luck, still freezing

Reverted to KSP version .25, everything works perfectly.... (copied to different hdd so i can still play; yay got my digital crack back! well, kinda...)

Re-updated to .90, game freezes after about 30 sec in the VAB.......... RABBLE RABBLE RABBLE!!!!

the following is the only NullReferenceException in the new output.log, and was from when the game froze:

deleting part liquidEngine

(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

NullReferenceException

at (wrapper managed-to-native) UnityEngine.MeshFilter:set_sharedMesh (UnityEngine.Mesh)

at SpriteMesh.CreateMesh () [0x00000] in <filename unknown>:0

at SpriteMesh.get_mesh () [0x00000] in <filename unknown>:0

at SpriteRoot.Delete () [0x00000] in <filename unknown>:0

at SpriteBase.Delete () [0x00000] in <filename unknown>:0

at UIListItemContainer.Delete () [0x00000] in <filename unknown>:0

at UIScrollList.RemoveItem (Int32 index, Boolean destroy, Boolean doEasing) [0x00000] in <filename unknown>:0

at UIScrollList.RemoveItem (IUIListObject item, Boolean destroy, Boolean doEasing) [0x00000] in <filename unknown>:0

at UIScrollList.RemoveItem (IUIListObject item, Boolean destroy) [0x00000] in <filename unknown>:0

at ApplicationLauncher.RemoveApplication (.ApplicationLauncherButton button) [0x00000] in <filename unknown>:0

at ContractsApp.OnDestroy () [0x00000] in <filename unknown>:0

(Filename: Line: -1)

Any other ideas anyone?

I really want to play with all the new features.....

Updated KSP Log: https://drive.google.com/file/d/0B7U2eHh0eg4BTTgzZzlzM2k4Nms/view?usp=sharing

Updated Output Log: https://drive.google.com/file/d/0B7U2eHh0eg4BXzl1aGRWQmFyRmM/view?usp=sharing

[bgeery]

I had to switch to using "-force-opengl -popupwindow" when moving to .90

[sal_vager]

There doesn't look to be anything obvious in your logs, just this line:

[RDTechTree]: No tech node found called Unresearcheable

This may be due to an older save that became corrupted, and as Steam installs on Windows place their saves in C\:users\application data\... this won't be effected by a reinstall.

I suggest finding the saves and checking for missing folders and zero length files, or just move the lot out and use Steam to replace the Scenario and Tutorial folders.

I also suggest not using -force-opengl or -force-d3d11 as neither of these are particularly well supported even by Unity3D.

Edited March 7, 2015 by sal_vager

[Claw]

The R&D Tech Tree warning is a standard warning. Sadly, the logs are quite fill with useless spam sometimes.

Obviously this is a tough problem, since it's leaving no trace in the log files. One of the things that changed in 0.90 was the inclusion of PPFX edge highlighting. That particular feature seems to cause some sneaky behavior.You might also want to try making sure that option is off, along with anti-aliasing. If you turn them off in the settings menu, you'll have to restart for it to take effect.

Also, the -opengl flags seem even more volatile in v0.90. It used to be that they would just sometimes cause problems, or sometimes not. Now it's either catastrophic or totally necessary. I believe this particular thing is due to a unity update.

Yet another thing to try, that unity updated, is full screen mode shenanigans. Try running in not full screen (or the other way around, if you've already been running not full screen). One thing that seemed to help a few people was using the -popupwindow flag. For this, I would recommend copying & pasting your KSP install to another folder. Then make a shortcut to KSP.exe. Edit that shortcut and include the command flag "-popupwindow" (without the quotes).

That's all I can think of off the top of my head. Unity made some changes that seem to cause graphics problems, and KSP's big graphics thing was adding the edge highlight (which is sort of hit-and-miss). Hopefully something in there will help.

Cheers,

~Claw