Jump to content

Optimization


Recommended Posts

Hello all, I am currently playing KSP on a bog standard Toshiba satellite laptop, I can't quite remember the model number but it only has 4GB of RAM, and a poor 1.8 dual core CPU and onboard graphics, The specifics elude me at the moment, partly due to shame, and partly due to me being at work and unable to check. But basically it falls just below the minimum requirements of KSP. Now it runs the game admirably on low settings and slogs on like a little trooper at between 30 and 20 FPS during normal single ship missions. Problem comes when I try running more than 150 or so parts on a ship, or when I'm docking two ships in orbit. Typically when docking my frame rate can drop as low as 2-10 FPS and when I launch a large complex rocket my craft occasionally just disintegrates at around 15km. Also when handling large rockets the game occasionally crashes to desktop when I try jumping in and out of the VAB (probably due to my little laptop cooking its CPU or lack of memory)

Now I've like to be able to perform big interplanetary surveys and whatnot, but I'm aware that this probably lies outside of the realms of possible with my hardware. What I would like to know is whether there is any means of improving the optimization and performance through a MOD or any other means to try and squeeze more power out of my sorry excuse for a laptop (sorry laptop) while I have reasonable computer skills I'm not as knowledgeable as I would like to be so any suggestions, even simple pointers might help

Right now I'm playing the vanilla game on almost minimum settings, but I recently installed Mechjeb just to try it (although I don't need it to succeed) and I have Scansat installed which I keep meaning to remove.

I'm aware that future updates might improve optimization but they also might end up adding more memory demanding features too so in the long run I will need a more up to date machine.

Any advise would be greatly appreciated and could vastly improve my enjoyment of KSP

:D

Link to comment
Share on other sites

You only need memory footprint reduction mods if you're having problems with memory, e.g. if your problem is swapping memory blocks to the swap file. Stock game does not use more than about 2 GB of RAM (beside memory leaks which will be hopefully fixed in future releases) and that should fit into the 4 GB you have.

Disintegration of your ship at 15 km is probably caused by too much stress on the construction - as your fuel tanks become emptier, engines are applying more force on connections above them.

Just make sure your maximum physics time step is not set to too high value in settings. Low FPS is a problem, but as long as the physics is applied in sufficiently small steps on your ships, they should behave normally (i.e. not spontaneously break) although you're watching them in slow motion.

Link to comment
Share on other sites

The crash to desktop when moving in and out of VAB (or when handling very large sub-assemblies within the VAB) is definately a RAM issue, and one I saw myself on my 2Gig lappy. The texture reduction fix posted by Taki117 should help with that.

Otherwise Kasuha is right in that the stock game cannot pull more than a certain amount of RAM (though I personally always thought it was 3.5G). It's worth taking a look at your background processes through the task manager (assuming Win) to see what else might be idling away your Memory. A surprising amount can disappear this way, I always forgot to axe chrome when gaming and browsers are pretty heavy footprint-wise.

Having SCANSat installed and not using it will be tying up a bit of RAM, though not too much, and MechJeb will be also negligible impact. Mods demand RAM mainly as the game starts, and the amount they suck depends pretty much entirely on the number of parts they add to the game (alongwith the size of the textures for those parts). This means MechJeb has a tiny footprint with just a couple of small parts, SCANSat also adds smallish parts, though a few more than MechJeb. Neither is particularly heavy, stay well away from packs like KW Rocketry/KSPInterstellar/NovaPunch, as each adds dozens of big parts.

Your best hope to increase playability is going to be the texture reduction mods.

Link to comment
Share on other sites

Otherwise Kasuha is right in that the stock game cannot pull more than a certain amount of RAM (though I personally always thought it was 3.5G).

The game cannot use more than 3.5 GB of memory, whatever mods you have installed. Except on Linux. It's because the game is 32-bit application and that is in turn because Windows release of Unity is unstable in 64 bits.

But the stock unmodded game usually uses way less than this limit. Especially if your machine limits you in other ways (low resolution of textures, low part counts etc).

Link to comment
Share on other sites

Thanks guys I'm sure these will help, I also read somewhere else in the forum that I can edit the Settings.cfg file to reduce ocean load distances and subdivisions which may help a little more. I will also kill some background processes while playing, disconnect my internet and turn off my anti virus then boosting KSP to an above normal processor priority in task man :)

Edit: is there any good part welding mods for 0.23 you can recommend, and what's the pros and cons of using them?

Edited by FREEFALL1984
Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...