KSP Dev Cycle

[BenHR]

I'd like to be able to play this game. I really would. But any and all loading screens STILL make me die. Sometimes, it crashes out of the blue. I'm hoping the new computer I'm building might help this out a bit, but that won't be done for months. However, I barely crash at all when it's a new major update. But it's the little updates that screw it up again, and that's what I'm stuck with most of the time. Today I got a satellite in orbit around Jool and attempted to make a Munar land and return mission, but it failed. The game crashed 7 or so times throughout.

[The Jedi Master]

I have not encountered that. Have you considered that it may be your computer?

Also, thousandth post

[swiftgates24]

I don't know about all these crashes. I've had none. Could be because I don't build crazy rockets like the rest of you...

Also, congrats Jedi Master! Now beat me (1,500-ish)!

[Tygroux]

Loading is totally messed up(read: extremely longer than before and what is normal) for a lot (not all) users.

It seems to be machine-dependent, but it's not even sure an upgrade will help.

[FITorion]

well for 1 we're still on .21.1 a .21.2 has not come out.

for 2 Most problems are caused by Mods. The stock game for which I have been playing since .18 has never crashed.

3. There is one know bug I'm aware off that causes a crash during scene changes that is a problem for those using Fraps. There is a workaround for it however... and they are working on a fix.

So... what was your problem again? How can we help you?

[BenHR]

I am using a one mod now, just the Chatterer mod. Though, that didn't affect crash rates. And I know we aren't in an X.2 yet, but I meant that in general. No FRAPS, so yeah. Chances are, it is my compy, but every 0.X.0 is always several magnitudes more stable for me than any 0.X.Xs. My current compy is a Pentium D box with a Geforce 9800, 3 GB of RAM with Windows XP 32. My new one will be an i5 3570 with that same 9800 (but eventually a GeForce 770 or something), 8 GB of RAM and Windows 7 64. I'm hoping that much more sauce will help. Though most often it's the game itself that crashes, this is also the only game that makes my graphics driver cause a BSoD, though that appears to be more that Nvidia's thing is derped on 32 bit OSs and VIA chipsets - neither of which will be in my new one, but both of which are existent in my current setup.

[OrbitusII]

KSP's 32-bit version maxes out at 4GB of RAM, and if you only have 3GB it may be that your computer runs out of RAM while changing scenes or performing big calculations and stuff. I know they added the new scene loading system to help prevent that, but there's always going to be one person that crashes even with that improvement.

I've noticed that the 64-bit version runs a little faster than 32, but it's not significant enough for me to recommend a 64-bit OS to everyone (although we are moving towards 64-bit for everyone). I would recommend getting that new computer soon, having improved stats (and a more up-to-date OS) should help.

[Guest]

Today I got a satellite in orbit around Jool and attempted to make a Munar land and return mission, but it failed. The game crashed 7 or so times throughout.

I wish I could sympathize but I have never seen problems on this scale, even with mods loaded. I would venture that there is either an issue with the older processor you're running with (Core2 chips don't have those issues either) or some other program running on your computer (maybe something not obvious).

[Rarity]

My game has been far less stable than past versions, but it was mostly due to having far too many parts added. I reinstalled and only added mods that were light on the part count, and now the game only crashes occasionally. It's easy to deal with now in comparison to before, but it would be nice if I could play with B9 and Firespitter again

[Guest]

My game has been far less stable than past versions, but it was mostly due to having far too many parts added. I reinstalled and only added mods that were light on the part count, and now the game only crashes occasionally. It's easy to deal with now in comparison to before, but it would be nice if I could play with B9 and Firespitter again

Download razer game booster, make sure it turns off everything pretty much (especially explorer) and run KSP with it in boost mode, gets rid of a lot of bloatware holding your CPU back. :-)

[Tiron]

My game has been far less stable than past versions, but it was mostly due to having far too many parts added. I reinstalled and only added mods that were light on the part count, and now the game only crashes occasionally. It's easy to deal with now in comparison to before, but it would be nice if I could play with B9 and Firespitter again

The problem's not Part Count, it's the textures. Unity massively inflates the size of the textures when it loads them into system memory for some reason: ISA Mapsat's maps, for example, are taking up about 600mb worth of memory with an average file size of 2.11mb for the completed maps, and 32kb for the blank placeholder.

Somehow it's using ~20MB per map, when even an uncompressed 32bit bmp is only 8mb at that size...

I suspect this is probably part of why the loads take so long: It's doing whatever horrible thing it does to inflate the textures and loading them into the system memory.

[FITorion]

Yeah XP 32 and 3 GB of ram sounds like your problem.

[KasperVld]

If you're having crashing issues please post a thread in the Support section of the forums and also please read the related sticky threads to see which information is needed. An unmodded install of KSP shouldn't crash even on Win XP 32 bit with 3GB of RAM.

[BenHR]

What's interesting is that it usually doesn't create a crash report. Though, sometimes it does. I should be sending those in, shouldn't I?

[KasperVld]

Yes, please create a support thread here: http://forum.kerbalspaceprogram.com/forumdisplay.php/58-Support-Bugs

And read this topic before doing so: http://forum.kerbalspaceprogram.com/showthread.php/24543-NEED-SUPPORT-Read-this-before-posting

[SRV Ron]

Yeah XP 32 and 3 GB of ram sounds like your problem.

And, chances are that computer, purchased from a big box store, is loaded with crapware running in the background, tying up cpu cycles, and hogging limited memory.

Currently, KSP is loading a texture for every part loaded even if that texture is the same. It is also loading everything into memory as well. Add mod parts, all of that loads too. Eventually, the developers will work out a solution where textures can be shared and parts loaded as they are needed. That would really speed things up and reduce the possibly of a out of resources crash.

A suggestion for the new computer, have it built to your specs by an independent shop that can then install the operating system without all of the crapware that hogs limited resources.

[leax256]

Pentium D.

this alone is reason enough for me to ask you to not complain. the devs have done alot to try to get the game to run on older hardware but they can only do so much. also if you running that old thing then you most likely are running a peta or sata gen 1 (we are on gen 4 now) hard drive. your gpu though is good enough for now.

Maybe in the future (non alpha) when it's optomised better you can have a better time.

As far as your new pc, hope it goes well.

also I have noticed longer loading times from the entire .21 update

3. There is one know bug I'm aware off that causes a crash during scene changes that is a problem for those using Fraps. There is a workaround for it however... and they are working on a fix.

my workaround, use xsplit

[BenHR]

Actually, this computer was a leftover from the office my dad works at and we got it a fresh hard drive and went from there. Not a whole lot of useless things running here. And, the new one is getting put together by me; I'm buying it part by part.

[JakeGrey]

If SRV Ron's suggestion is impractical, install Windows from scratch; use the license key on the side of the box and torrent a copy if you have to.

Long load times are one of those things you're just going to have to live with for the time being though, at least if you want to play anything but stock. I suggest buying a tablet or small netbook and settling in to browse the net or read an ebook while you wait, because it's also useful for those long missions when there's not much to do between course correction burns.

[boxman]

I am using a one mod now, just the Chatterer mod. Though, that didn't affect crash rates. And I know we aren't in an X.2 yet, but I meant that in general. No FRAPS, so yeah. Chances are, it is my compy, but every 0.X.0 is always several magnitudes more stable for me than any 0.X.Xs. My current compy is a Pentium D box with a Geforce 9800, 3 GB of RAM with Windows XP 32. My new one will be an i5 3570 with that same 9800 (but eventually a GeForce 770 or something), 8 GB of RAM and Windows 7 64. I'm hoping that much more sauce will help. Though most often it's the game itself that crashes, this is also the only game that makes my graphics driver cause a BSoD, though that appears to be more that Nvidia's thing is derped on 32 bit OSs and VIA chipsets - neither of which will be in my new one, but both of which are existent in my current setup.

Your issue in this case is that you are using a 32bit OS. I had exactly the same issues before i upgraded to win7. I was lucky to be able to have a couple of launches without a restart.

[boxman]

If you're having crashing issues please post a thread in the Support section of the forums and also please read the related sticky threads to see which information is needed. An unmodded install of KSP shouldn't crash even on Win XP 32 bit with 3GB of RAM.

It definitely did in my and others experience. Would crash with a error log complaining about not having enough ram to allocate even though I had 4gigs of ram and did not use a single mod.

[BenHR]

I hope my original post didn't come off as insulting. I really love this game. It's just those crashes that I myself have been experiencing are painful to the core. It even corrupted my save once, but I used a previous quicksave to salvage it. Funnily enough, that gave me a second chance to land a rover I crashed, and that second time I made it. But yeah, I just made the Support thread, with links to all the important things.

Edited August 31, 2013 by BenHR
Run on sentence.

[leax256]

Actually, this computer was a leftover from the office my dad works at and we got it a fresh hard drive and went from there. Not a whole lot of useless things running here. And, the new one is getting put together by me; I'm buying it part by part.

a newer hd is good however note that running a like a newer sata on an older one will limit the speed to the slowest one

[BenHR]

a newer hd is good however note that running a like a newer sata on an older one will limit the speed to the slowest one

Yeah, I know that. It's isn't a huge deal, really. The one hard drive I have now works at 3 GBit/s. Dunno how much my current mobo supports, but I know the one in my new computer has four 3 Gbit plugs and two 6 Gbit plugs. The additional hard drive I'll be getting for my new box will work with 6 Gbit.

[Tiron]

a newer hd is good however note that running a like a newer sata on an older one will limit the speed to the slowest one

I hope you're referring to the fact that SATA is backwards and forwards compatible. So that if either the motherboard or the hard drive have an older version than the other one, it'll still work, but only at the best speed the older part can handle.