Jump to content

ksp uses WAY TOO MUCH RAM


Recommended Posts

why is this a problem you may ask ?: because despite it takes  40  minutes of initializing it takes another 30 minutes for the start menu this is extreme performance drop , but the game crashes reporting something like steam error this happens due to autocrash occured because the steam gets shutted down by the system from excersive ram usage which totally makes the game unplayable how the performance drop ?? simply by virtual ram the system uses the hard drive as a (secondadry) ram and the ksp won't be playable the recommended ram specs for kerbal space program is 4GB (and i have 8gb) (and disabling virtual ram will result in a BSOD in intializing) mods installed (70 total) , :

KSP: 1.9.1 (Win64) - Unity: 2019.2.2f1 - OS: Windows 10  (10.0.0) 64bit
ClickThroughBlocker - 0.1.9.5
Filter Extensions - 3.2.4
Toolbar - 1.8.0.5
ToolbarControl - 0.1.9.4
Airplane Plus - 26.0.5
B9 Animation Modules - 1.7
B9 Part Switch - 2.16
B9 Aerospace Procedural Parts - 0.93
Community Category Kit - 5.0
Community Resource Pack - 1.3
CommunityTechTree - 3.4.1
ConfigurableContainers - 2.4.8
DecouplerShroud - 0.7.2
DeployableEngines - 1.2.1
DMagic Orbital Science - 1.4.3
DynamicBatteryStorage - 2.1.5
EngineIgnitor - 1.3.6.2
ExtraplanetaryLaunchpads - 6.7.2
Firespitter - 7.15
Fuel Tanks Plus - 2.0.2
Interstellar Fuel Switch - 3.14.2.1
JanitorsCloset - 0.3.7
JSIAdvTransparentPods - 0.1.22
RasterPropMonitor - 0.31.3
KAS - 1.5.7239.36651
Kerbal Engineer Redux - 1.1.7.1
Kerbal Foundries - 2.4.8.18
KerbalHealth - 1.4.2
Kerbalism - 3.7
Kerbalism - 3.7
Feline Utility Rover - 1.2.11
Kerbal Inventory System - 1.24.7279.41031
KramaxAutoPilotContinued - 0.4
KSP-AVC Plugin - 1.4.1.4
KSPWheel - 0.16.14.33
Modular Rocket Systems - 1.13.2
Docking Port Alignment Indicator - 6.8.6
NearFutureAeronautics - 1.0.4
NearFutureConstruction - 1.2.2
NearFutureElectrical - 1.1.1
NearFutureExploration - 1.0.6
NearFutureLaunchVehicles - 1.3
NearFutureProps - 0.6.2
NearFuturePropulsion - 1.2.1
NearFutureSolar - 1.2.1
NearFutureSpacecraft - 1.3.1
Photon Sailor - 1.4.11.5
Kerbal Planetary Base Systems - 1.6.11
RealChute - 1.4.7.6
DeepFreeze Continued... - 0.28
SCANsat - 1.1.8.14
SignalDelay - 0.2.11
SolarScience - 1.2
SpaceY Lifters - 1.17.2
StationPartsExpansionRedux - 1.3.4
StationScienceContinued - 2.6
TimeControl - 2.9.8
TweakScale - 2.4.3.11
VesselMover - 1.9
KSP Interstellar Extended - 1.25.13.5
WildBlueTools - 1.76
Kerbal Actuators - 1.8.2
Buffalo - 2.8.1
Classic Stock Resources - 1.1.1
Deep Space Exploration Vessels - 3.4.1
Kerbal KIS Items - 2.1.7
Mark One Laboratory Extensions - 1.21.1
Pathfinder - 1.35

Link to comment
Share on other sites

Running a large list of parts heavy mods on an older/less powerful PC will obviously make the game run slowly. Be ruthless and cut down on your mod use: scrap anything you don’t absolutely need, sacrifice some crafts if you have to to ditch another mod and close everything else on your PC to keep the memory free. Not sure why you need all those mods for the stock solar system, especially KSPIE which is monstrous overkill. I can regularly use 8 or in some cases 10GB of RAM running KSP.

The game loads everything in when it starts so having many gigabytes of extras will cause very slow load times especially with a slow hard drive. Again, removing what you don’t need will help with this and you can delete parts you don’t want/need from a mod and just keep the few that you do.

RAM isn’t very expensive so depending on your PC it might be possible to upgrade your PC relatively cheaply which will make the game run faster; likewise a small SSD isn’t too expensive and it will make a big difference as SSDs are much faster than a conventional hard drive and even an external SSD running through a USB3 port could dramatically reduce your load times. The best (and cheapest!) option is still to reduce your mod count, getting rid of anything you don’t desperately need and then keeping it low despite the appeal of shiny new mods (or when Kopernicus gets 1.9.x compatibility as planet packs use a lot of RAM too).

Link to comment
Share on other sites

Having multiple versions of the same mod is not the problem, but indicative of the root cause: not making any selection in installed mods at all.

 

Try running KSP without mods and then add the ones you really want back in one by one. Part mods tend to come with texture files which gobble up memory rapidly, so be extra selective with those when you have limited system resources.

 

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...