Which mods/parts consume a lot of memory

[leops1984]

I run a KSP setup with a... rather excessive amount of mods, so even with ATM I get some crashes. Is there a way to tell from within the game which mods and/or parts are consuming the most memory?

[Dkmdlb]

You could start by checking the size of the mod folders.

[jwenting]

each component adds data, each texture adds data relative to its size. So packs with many components and high detail textures add a lot of data.

Mods with only a few components and/or no textures add less data.

So for example KER adds very little, KW adds a lot.

[NathanKell]

Let us assume you use ATM (and therefore TGA textures will be compressed; stock KSP has an issue where they won't).

Let us also ignore anything except textures, since models take up next to no memory, and cfgs even less.

All textures in GameData will be loaded by KSP, and converted to DXT1 (if they are 3-channel RGB) or DXT5 (if they are 4-channel RGBA). The only exception are textures flagged as normal maps; these will be left uncompressed.

DXT1 has a compression ratio of 6:1. DXT5 has a ratio of 4:1. That means that a 1024x1024 DXT1 texture will take about 512KB of memory, and a DXT5 of the same resolution will take 1MB.

Note that this has very little relation to size on disk. MBMs are uncompressed on disk, so they will take up 1/6 or 1/4 their disk space in memory. PNGs, by contrast, can have much higher compression ratios than DXT; a 200KB PNG might end up taking 1MB of memory.