[Question] Is there a way to estimate RAM load per mod?

[hypervelocity]

hi guys!!! hope you are doing great!

i had a quick question as im trying to optimize my KSP install - is there a way to calculate the RAM load per mod in order to know which mods are making the game heavier??? im really close to the 3.5gb limit and i want to turn it down a bit!

any help or pointers are greatly appreciated!!!!! :D

[Mecripp]

The only way, I can think of is to make a stock install and check how much ram is used and the one by one change the mods you use each time checking ram but that's only going to give you at load.

This has been ask more then once good luck.

[hab136]

As general advice, the biggest mods are going to be beautification (clouds, textures) and then part packs.

[hypervelocity]

thanks a million guys!!! trying to have RSS+RO(and all its suggestions)+AVP is proving to be a bit tricky

[Kerbas_ad_astra]

In general, the size of a mod's folder will correlate to how much RAM it will require (since KSP loads the stuff from the folder into memory during startup). A tool like WinDirStat can visualize what the costliest folders and parts are so that you can plan accordingly.

Bear in mind that this is only a rough estimate. Anecdotally, I've noticed that clouds, planets, and IVAs and props seem to require more memory in-game than they do on-disk, as they generally need to use non-DDS texture formats.

[Van Disaster]

It's practically all textures - problem is they're compressed on disk, there might be some sort of image browser app that can estimate uncompressed size. There's some things like Astronomer's clouds which use odd size textures, I'm fairly sure their footprint will be the next power of 2 up once they're in memory... I resized all mine, did make a difference.

DX11 mode will unload about a GB of textures from main memory once they're dumped to VRAM. Note you can still crash hitting the 3.5GB limit when you're loading, just have more free memory while you're playing.