Even with 0.9 still crashing

[ferreiros]

Dear Community even after some months of waiting i am still getting a CTD when going from Menu through loading screen. here ist the bug report.

btw i tried both force openGl and standart KSP 32bit start...both same result. Menu and then crash while loading and thats it since 3 or 4 months. I am fed up. I have the feeling it is due AMD Catalyst driver. that is what my guts tell me.

http://m.uploadedit.com/b043/1418755441289.txt <--- output log

http://m.uploadedit.com/b043/1418755656501.txt <-- error log

[ferreiros]

Little Update: Even with the change "Texture-Quality=1" still get a crash while loading into to Base

[Inglonias]

This is probably a dumb question, but have you tried a completely fresh clean install of KSP?

[ferreiros]

Its not a dump question ^^. Yes i did three times... but without success

P.S.: I`ve had the exact same problem with .25. Even the support was clueless....I came to the conclusion to give up and decided to wait but with no success -.-

P.P.S.: Ok fellas now its getting redicoulus...it came into my mind to watch KSP Credits and guess what....CTD. Something is realllly odd.

Edited December 16, 2014 by ferreiros

[Claw]

It certainly does look like your video card is having problems. Especially since this line is present:

GL: disabling render-to-cubemap due to Radeon driver bugs

GL: disabling mipmapped render textures due to Radeon driver bugs

GL: Detected 0 MB VRAM

That being said, your error.log also shows this:

1024 MB physical memory [1024 MB free].

2048 MB paging file [1024 MB free].

0 MB user address space [2519 MB free].

So what I'm really suspecting is that you might have two problems going on.

Memory I'm really impressed that KSP even loads for you with only 1GB of physical memory available. I'm guessing it takes a long time to happen, since your computer is probably using a lot of virtual memory.

It is possible to get KSP below the 1GB mark to at least see if the game will run with your video card, but you have to be really aggressive and willing to give up some things.

Go do the GameData directory. In there, you'll see two folders. The NASA one and a Squad one. Delete or move the following folders...

GameData\NASAmission\Parts - Move out all the subfolders

GameData\Squad\SPP - Move out all the subfolders

GameData\Squad\Parts - Move out all the subfolders

Also, edit your settings.cfg and make sure the TEXTURE_QUALITY line says "TEXTURE_QUALITY = 3" (without the quotes of course). Make sure it's all caps, and an underscore, not a dash.

Start up the game and see if it crashes. Also monitor your memory usage by bringing up the windows task manager.You will not have any parts available in game, but at least you can poke around and see if it crashes.

If that's not working, you can also try adding the OpenGL flags. It probably won't save you much more memory than TEXTURE_QUALITY = 3. And OpenGL is pretty flaky to begin with, so it might be causing problems itself.

If this fixes things, then I would say you'll need to upgrade the memory capacity of your computer (if you can). Otherwise if you can't, you can slowly add some parts back to those folders and see if you can stay below your memory constraints.

Video Card

Update your video drivers. If they are updated, see if you can regress them a couple versions and see if that helps. Sometimes when drivers get updated, they break things.

Also, check out this thread. There are a few random things you can try that often help with crashes.

Good luck,

~Claw

[ferreiros]

thats very strange since i have 8GB Ram >_> . Also i have in the past played this game over 200hrs and enjoyed it without problems until patch 0.25 came...thats when it turned bad. So basically theproblem is that either my Catalyst 14.4 doesnt support KSP OR KSP doesnt aknowledge my 8GB RAM + 1GB VRAM. here is my DXdiag

http://txt.do/o8hh or http://textuploader.com/o8hh!

Edited December 17, 2014 by ferreiros

[Claw]

Hmm. I see also that you have a Phenom processor. Give this a try:

AMD Phenom processor

Phenom CPU's can still crash even with all fixes in this thread applied, this is due to the Phenom's Turbo Core technology which can cause instability in KSP. You can disable Turbo Core in two ways:

Add the following line to the target box of a shortcut after KSP.exe: "-force-gfx-st" (without the quotes)

Disable it in the Bios / UEFI

[ferreiros]

I will give it a try later although i am not well used to BIOS...F9 was it right ?

P.S.: Thank you for your help Claw. Nevertheless my core is almost 6 years old its a Phenom I not II and the mighty internet says nothing about my Phenom having that turbo technology. Well when i get home i will give it a try.

Edited December 17, 2014 by ferreiros

[vexx32]

It changes depending on which company built your motherboard. The only place you're likely to find that info is on their website, or in the manual (if you have it).

[ferreiros]

Dear Community,

thank you all for your help but even with -force-gfx-st and looking into bios...to my regrett no success...after putting -force-gfx-st inside i dont even get any output-logs just a very very claen crash to desktop. As Claw said before there got to be a problem with my radeon drivers and KSP. Reason why is i red somewhere that Linux Radeon software causes Problem with KSP maybe there is something close to windows too but numbers of people having that problem are a minority. Btw with my almost 7 Years old rig i still play Dragon Age Inquisition on relativly good quality thanks to mantle. Therefor i think it has to do something with KSP vs. Radeon Driver.

@Claw: I removed also all folders you suggested without prevail. But here it comes one of the great KSP mysteries...the KSP Demo works fine .....

[ratchet freak]

version 0.90 didn't improve the unity instability

Have there been any improvements to the 64-bit build?

Unfortunately not, the Windows 64-bit version is still very unstable and 0.90 has introduced a loving handful of new issues with the win64 build. The 64-bit issues are definitely on the radar though, and we do want to fix the issues if and when possible. If you happen to find any sort of fix or workaround to these issues, let us know. We appreciate any input that might better help us find a greater solution to these issues.

[ferreiros]

Anyone an Idea where i can download a version before 0.25 ? last version working for me was 0.19 i guess

Edited December 17, 2014 by ferreiros

[cartman]

Do you by any chance use Raptr? That caused crashes right after loading the game. I know not exactly your case but it's worth a try.

Edited December 18, 2014 by cartman
spelling

[ferreiros]

@cartman thx for the hint. But that also didnt help. Anyone an idea where i can download old kerbal versions ?

[Claw]

@cartman thx for the hint. But that also didnt help. Anyone an idea where i can download old kerbal versions ?

If you are using Steam, you can click on the Beta option and select "Last stable release."

If you bought from the KSP store, log into your account as if you're going to download the new version. Below the link to the current release, there is another link that goes back to the previous version.

That's as far back as you can go with the legitimate routes. You could also try emailing directly to KSP support and see if they can do anything about the downloads. I don't know Squad's official policy on that one.

Cheers,

~Claw

Edited December 19, 2014 by Claw

[ferreiros]

@Claw thx for the advice, but i have the steam version and even if i download the last stable version i get the 0.25 version which already didnt work for me. Also i wrote th the KSP team but i remember the support team was always short on manpower and will take long for the smallest reply... well i am back to Play the Demo V.0.18...at least that is stable ^.^ . Wish they could send me a link to a mysterious place with downloads.

[ferreiros]

Sigh...still no update on the side of the support >_>

[sal_vager]

Have you got an output_log.txt where you don't use openGL please?

[ferreiros]

My problem currently is i get Clean CTDs so no output logs >_>

P.S.: This game is reallly temting me....now i just dont get output logs.....

P.P.S.: Seriously i have to install thwe game for the fifth time in 2 days in hope to get output logs -.-

Status Update: Anger Keeps growing, fresh install but still no output_logs

Status Update 2: lmau when i press Alt + F12 i get insta CTD

Status Update 3: Well since i dont get a output log currently i can only offer my last log from 18th december http://m.uploadedit.com/b043/1419020789423.txt

Edited December 19, 2014 by ferreiros

[ferreiros]

FInalyy i got an output log, but it is from the last stable Steam version which is 0.25...but well same problem here as with 0.9 http://m.uploadedit.com/b043/1419068502322.txt

[vexx32]

Even with 'clean' CTDs, there will still be an output_log.txt file generated. You'll find it in the KSP_Data folder (or, if you're running the 64-bit version, it'll be in the KSP_x64_Data folder).