Need help paring down mods

[Dacker]

Hi. I need some advice on paring down my mods and I hope this is the right place to post. I have the following installed at the moment:

Note that B9-Aerospace is not actually installed, it's just the few .cfg files that one of the mods installs (USI MKS I think).

I would like to at least keep using Deadly Reentry, KW Rocketry, TAC life support, SCANSat, and RemoteTech 2. I really would like to use USI's MKS mod so i can build nice orbital and planetary bases. I think it takes a lot of resources, though.

I run in x64 mode, but I have also tried x32 mode (changing the ActiveTextureManager to x32 bit of course). I hit over 3.5GB in x32 mode with all of these mods so of course it crashes. In x64 mode I hit over 4GB, but I can usually run it okay with all of the mods minus MKS (or any other mod for that matter - It's like that's the straw that broke the camel's back)

I don't know enough about mods, but do you see anything on my list that maybe I should dump that also happens to fit in the same memory footprint that MKS does? I play in Sandbox mode. I'm just having a tough time deciding what mods to dump in favor of MKS, and I don't know which ones are the most resource hungry and least impactful on enjoyment of the game. Maybe you can make a suggestion on what to dump so i can get down below 3.5GB memory usage and use x32 KSP? Here are my system specs:

- Windows 8.1 x64

- i7-4770k (not overclocked)

- 8gb ram

- Asus Maximus Formula VI motherboard

- 2x GTX 780 video cards in SLI

- 500gb Samsund SSD drive, with two 3gb Western Digital drives in RAID 1

- 2560x1440 monitor

Oh, and all mods are up to date as of yesterday

Thank you!

[vexx32]

Essentially, anything that contains a lot of parts is the best place to start.

[Hurry- Starfish!]

Apart from removing parts, you can edit your ATM config to lower your RAM consumption somewhat at the cost of texture quality. Or you could try the Load on Demand mod, that one might also help.

[NathanKell]

You can also selectively lower the resolution of certain mods, or parts of mods. ATM is very flexible.

For instance, if you don't use IVA much (or don't use the IVA of certain parts much) you can increase the scale factor (and lower final resolution). You can also selectively delete parts, like various Squad fuel tanks, or KW nosecones, or NP2 aux motors.

[Dacker]

I really appreciate the help. You are right in that I rarely use IVA. I didn't realize the customization of ATM. I've poked around in the config file and the examples and I understand the concept of increasing the scale and thereby lowering the resolution of the texture. What I am unsure of is how I can do that with individual parts of a mod. I am not sure how to isolate a part to raise the scale. I've looked through the various mod cfg filed included in the boulderco/activetextexturemanagerconfigs folder but just cannot figure this out.

If you get the time, could you provide an example cfg entry I can use to raise the scale on such a part?

Also, I had never heard of the Load on Demand mod before but now that I have I will definitely give it a try.

[NathanKell]

Here's an example that overrides TVPP's scale to be 4.

ACTIVE_TEXTURE_MANAGER_CONFIG
{
	folder = TVPP
	enabled  = true
	OVERRIDES
	{
		TVPP/.*
		{
			scale = 4
		}
	}
}

You could put, say, Squad/Space/.* in as an override in the Squad config and it would only apply to stuff under the Space/ path. (The override paths are in regular expression form, if that helps).

[Dacker]

Got it - that does help. Really appreciate the assistance!

[neder]

I would suggest running 32 bit with Active Texture Management installed. If you're still running out of ram you can force the game to use open GL instead of directx.

Instructions here: http://forum.kerbalspaceprogram.com/threads/84203-Less-memory-usage-by-using-OpenGL

I run 32 bit with about 60 mods installed including all the memory hogging ones and I'm using between 2.5 and 3 GB ram.

[Dacker]

You're not going to believe this, but I now have all of the mods running (plus a few extra) by deleting ATM and running 64 bit. No clue why. I thought maybe I had left the 32 bit version of ATM installed so I deleted it againt and reinstalled 64 bit and it crashed again. Removed ATM once again and no issues. In 64 bit my memory usages is around 4.5gb

Very odd, but hey, it works.