[1.0][Release-5-0][April 28, 2015] Active Texture Management - Save RAM!

[Whirligig Girl]

will it lower the visual quality of the textures?

[Galane]

Where were you when this started happening? Did you modify the config at all?

I just removed the B9 and KW folders from the folders section then changed it to this

FOLDERS
{
	folder = Squad/
	folder = BoulderCo/
	folder = nothke_DROMOMAN/
	folder = MagicSmokeIndustries/
	folder = HooliganLabs/
	folder = Kethane/
	folder = StretchyTanks/
	folder = KAS/
	folder = Keramzit/
	folder = BoJaN/
	folder = KSPX/
}

The rest of the cfg I left alone. Deleting all those then running and quitting KSP didn't properly restore the textures. Ships were ghostly white so I extracted the Squad folder, copied it over the existing one and did the same for all those mods.

I replaced the 2-4 version with the 1-1 version and it works. I'm running on XP with only 2 gig RAM. The last time I ran into UI textures going wonky like this was with KSP .21, before I found PolecatEZ's reduced size Squad textures, which I'm not currently using with this AMR mod.

[rbray89]

I just removed the B9 and KW folders from the folders section then changed it to this

FOLDERS
{
	folder = Squad/
	folder = BoulderCo/
	folder = nothke_DROMOMAN/
	folder = MagicSmokeIndustries/
	folder = HooliganLabs/
	folder = Kethane/
	folder = StretchyTanks/
	folder = KAS/
	folder = Keramzit/
	folder = BoJaN/
	folder = KSPX/
}

The rest of the cfg I left alone. Deleting all those then running and quitting KSP didn't properly restore the textures. Ships were ghostly white so I extracted the Squad folder, copied it over the existing one and did the same for all those mods.

I replaced the 2-4 version with the 1-1 version and it works. I'm running on XP with only 2 gig RAM. The last time I ran into UI textures going wonky like this was with KSP .21, before I found PolecatEZ's reduced size Squad textures, which I'm not currently using with this AMR mod.

After you delete the folders from the list, you have to run KSP and quit. I'm thinking of changing this so it doesn't replace the textures on-disk, just in-memory, but that could increase loading times by a good margin.

[bulletrhli]

After you delete the folders from the list, you have to run KSP and quit. I'm thinking of changing this so it doesn't replace the textures on-disk, just in-memory, but that could increase loading times by a good margin.

I believe a mixture of both may help, definitely worth testing on your end.

[Galane]

After you delete the folders from the list, you have to run KSP and quit. I'm thinking of changing this so it doesn't replace the textures on-disk, just in-memory, but that could increase loading times by a good margin.

Like I said Deleting all those then running and quitting KSP didn't properly restore the textures.

[Donziboy2]

Like I said Deleting all those then running and quitting KSP didn't properly restore the textures.

Where you using the Texture Reduction packs on those 2?

[Galane]

I'm not using B9 or KW. The only texture reduction pack I've used was the Squad one, but I deleted and replaced the Sqaud folder to put it back to stock before trying any version of the texture compressing mod.

[ddenis]

Just tried new KW for 0.23 with experimental build 2.4 - all parts were white, without any color at all.

[Surefoot]

Just restart the game ?

[gardocki]

I found the cause and solution for anybody having freezes during loading on some mods:

Parts or interiors using single-pixel textures are will freeze when trying to compress them. Add an exception for that part's folder under the Overrides section of the config file. This worked for me with KSP interstellar. I now have that, KW rocketry, B9 and about 25 assorted part packs all running in under 3gb of memory.

[rbray89]

I just uploaded a new version with two different profiles for memory reduction. This new change also removes the need to write to the disk and convert the mbms, and will automatically revert the mbm change,

BUT YOU HAVE TO RESTART AFTER THE FIRST LOAD, OTHERWISE THE STOCK TEXTURES WILL BE WHITE.

I also noted that the KW normal maps are somehow loaded as non-readable, so I have to figure out a way to read those. Still, with the aggressive settings, when running with KW and B9 I'm running just over 1.5Gb without texture reduction packs.

[rbray89]

I found the cause and solution for anybody having freezes during loading on some mods:

Parts or interiors using single-pixel textures are will freeze when trying to compress them. Add an exception for that part's folder under the Overrides section of the config file. This worked for me with KSP interstellar. I now have that, KW rocketry, B9 and about 25 assorted part packs all running in under 3gb of memory.

Ahh... ok. Well I'll add a conditional for those then.

[rbray89]

I found the cause and solution for anybody having freezes during loading on some mods:

Parts or interiors using single-pixel textures are will freeze when trying to compress them. Add an exception for that part's folder under the Overrides section of the config file. This worked for me with KSP interstellar. I now have that, KW rocketry, B9 and about 25 assorted part packs all running in under 3gb of memory.

Should be fixed in 2.6.

[Rivvik]

So far, it's working. Game loaded no prob...there is ONE mod I got a white texture/missing texture for, so far...kinda funny actually...its your low res clouds mod on kerban. :3

[rbray89]

So far, it's working. Game loaded no prob...there is ONE mod I got a white texture/missing texture for, so far...kinda funny actually...its your low res clouds mod on kerban. :3

HUH? Which profile are you using? Aggressive or basic?

[bulletrhli]

I noticed something weird with the aggressive version 2.5. I added Deadly Reentry into the config and when I loaded the save file it says that the part was missing and it could not load a few of my ships. I then checked the debug (alt+f12) to see what textures were loaded and it was there. I have yet to test with the basic version. This may or may not have to do with the mod, but I thought I would say something just incase.

*** Edit

It seems to have been removed from my tech tree. I had installed KAS afterwards so maybe that had caused the issue but I am unsure at this time.

Edited December 31, 2013 by bulletrhli

[rbray89]

I noticed something weird with the aggressive version 2.5. I added Deadly Reentry into the config and when I loaded the save file it says that the part was missing and it could not load a few of my ships. I then checked the debug (alt+f12) to see what textures were loaded and it was there. I have yet to test with the basic version. This may or may not have to do with the mod, but I thought I would say something just incase.

Ah, I need to update that in the readme. Some textures can't be marked as non-readable, so they have to be added to the "LEAVE_READABLE" list in the config. The textures it complains about are those textures. I hope to compile a list and gradually add the big part mods to the config so everything will work by default. That is why currently, I only compress the textures.

[rbray89]

So far, it's working. Game loaded no prob...there is ONE mod I got a white texture/missing texture for, so far...kinda funny actually...its your low res clouds mod on kerban. :3

Should be fixed in 2.6

[FenrirWolf]

Okay, so the aggressive version doesn't modify files anymore. I suppose that means it has a longer boot time in exchange for that, right? Also, is at least the 1-1 style compression applied to folders not added via the config file, or are they left unaffected unless added?

[rbray89]

Okay, so the aggressive version doesn't modify files anymore. I suppose that means it has a longer boot time in exchange for that, right? Also, is at least the 1-1 style compression applied to folders not added via the config file, or are they left unaffected unless added?

Exactly. The textures are basically re-loaded without the noread restrictions. Everything that can be is compressed.

[LameLefty]

Just tried this version today and made sure to follow the instructions ... wow! When KSP is running on my system it typically uses in the range of 1.5 - 3.5 gigabytes. With this plug-in, my game right now is running at 755 megabytes.

[FenrirWolf]

Yeah, 2.6 seems to be a winner so far.

[rbray89]

I noticed something weird with the aggressive version 2.5. I added Deadly Reentry into the config and when I loaded the save file it says that the part was missing and it could not load a few of my ships. I then checked the debug (alt+f12) to see what textures were loaded and it was there. I have yet to test with the basic version. This may or may not have to do with the mod, but I thought I would say something just incase.

*** Edit

It seems to have been removed from my tech tree. I had installed KAS afterwards so maybe that had caused the issue but I am unsure at this time.

hmmm... does it exist in the sandbox mode?

[Dante80]

rbray, a question. Right now, 2.6 aggressive destroys my memory (crashing while using about 3.5gb when the loading bar finishes), while 1.1 with the exact same gamedata folder loads ok with about 2.7gb at the start screen. My gamedata folder is about 1.8gb in size, using a lot of mods.

If I understand correctly, 2.6 aggressive has a config file where we can place folders and parts and assign instructions on compression, overrides etc. Everything not specified in the config is compressed with the 1.1 method.

Might my problem be that the 1.1 compression comes at the end of loading instead of in-the-go? Could this be altered in some way?

[Tourman]

Having lots of problems with this mod now, ever since 2.4, some textures refused to load. With 2.4, none of the textures from Remote Tech mod would load - all the models were white. Now, Kethane, RT and even the stock Science lab refuse to load textures with 2.6.