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

[Virtualgenius]

Thats cool cant ask anymore from you I am a unique situation and I have always been a problem child

[rbray89]

Thats cool cant ask anymore from you I am a unique situation and I have always been a problem child

Haha... If someone else presents the same situation, I might be able to make some correlation with some specific mod, but until then we are out of luck I think.

[rbray89]

Haha... If someone else presents the same situation, I might be able to make some correlation with some specific mod, but until then we are out of luck I think.

Actually, I think there is one other option. You could copy all your mods into a zip or 7z/gzip/tar.gz and upload it to dropbox/google drive/etc so I can download and mess around with it. You can PM or post the link, whichever you feel more comfortable with.

[Virtualgenius]

Ok I have finally got this to work your not going to believe this but I went through each line of the log to see what it was *****ing about and I found folders that where not in the correct place for example Bobcats soviet pack some of the folders that have the resources and spaces where not in the default location, probably a fail copy and past by me somewhere along the line but to cut this short its working, it doesnt like non default location for mod folders.

This is using V27 Basic

WRN 17:56:11.458] [HighLogic]: =========================== Scene Change : From LOADING to MAINMENU =====================

[LOG 17:56:12.993] AddonLoader: Instantiating addon 'TextureCompressor' from assembly 'TextureCompressor'

[LOG 17:56:12.994] TextureCompressor: Memory Saved : 847445222B

[LOG 17:56:12.995] TextureCompressor: Memory Saved : 827583kB

[LOG 17:56:12.995] TextureCompressor: Memory Saved : 808MB

Edited January 4, 2014 by Virtualgenius

[Raptor831]

Quick question: I see the texture errors in the log file, but how do I fix it inside this mod's .cfg file?

I've got two error types occurring:

UnityException: Texture 'KOSMOS/Parts/Structural/Kosmos_VA_RRV_LockDown/VA_Lockdown_NRM' is not readable, the texture memory can not be accessed from scripts. You can make the texture readable in the Texture Import Settings.
...
...
GameDatabase: Texture 'KOSMOS/Parts/Structural/Kosmos_Salyut_1.5-1_Taper/NRM' requested as normal map but texture is not a normal map and is not readable

In the .cfg file there's the "Keep Readable" section and the "Normals" section. Which section do I place each texture that causes an error? Do they each need to be in different sections of the .cfg file?

[rbray89]

Quick question: I see the texture errors in the log file, but how do I fix it inside this mod's .cfg file?

I've got two error types occurring:

UnityException: Texture 'KOSMOS/Parts/Structural/Kosmos_VA_RRV_LockDown/VA_Lockdown_NRM' is not readable, the texture memory can not be accessed from scripts. You can make the texture readable in the Texture Import Settings.
...
...
GameDatabase: Texture 'KOSMOS/Parts/Structural/Kosmos_Salyut_1.5-1_Taper/NRM' requested as normal map but texture is not a normal map and is not readable

In the .cfg file there's the "Keep Readable" section and the "Normals" section. Which section do I place each texture that causes an error? Do they each need to be in different sections of the .cfg file?

KOSMOS/Parts/Structural/Kosmos_Salyut_1.5-1_Taper/NRM would be added to the normal map section, and KOSMOS/Parts/Structural/Kosmos_VA_RRV_LockDown/VA_Lockdown_NRM would be added to the make readable section.

[rbray89]

hmmm interesting. Don't know why this would work this way, but I'm glad you figured it out.

[Raptor831]

KOSMOS/Parts/Structural/Kosmos_Salyut_1.5-1_Taper/NRM would be added to the normal map section, and KOSMOS/Parts/Structural/Kosmos_VA_RRV_LockDown/VA_Lockdown_NRM would be added to the make readable section.

Thanks. Just wanted to double check because I was confusing myself.

[SpeedyFarrar]

I solved my problem, it turned out that I screwed up something in the config file. 2-7 runs great now, KSP is using 2.5GB, down from 2.9GB with 2-6

[tygoo7]

This is probably one of the best mods ever. With my install I have WAY too many mods and would get to like 3.4gb and crash but when I installed the experimental aggresive I got down to 2.5gb! Thank you!

[Ruedii]

Is there a way to make the alpha-dropping selective in future versions so it can be re-included in the aggressive version?

[CleverLikeMe]

I'm getting very little memory reduction, especially compared to texture reduction packs. Using latest version 2-7 aggressive, I get 348mb memory saved according to the log file. Running interstellar, KW rocketry, kethane, MJ, infernal robotics, FAR, and procedural fairings.

[rbray89]

Is there a way to make the alpha-dropping selective in future versions so it can be re-included in the aggressive version?

I thought about it, but realistically, mbms are already setup to use the correct format, and alpha dropping ruined the normalmaps.

[rbray89]

I'm getting very little memory reduction, especially compared to texture reduction packs. Using latest version 2-7 aggressive, I get 348mb memory saved according to the log file. Running interstellar, KW rocketry, kethane, MJ, infernal robotics, FAR, and procedural fairings.

You can increase the scale value in the config to shrink the textures further, and/or disable mipmaps and/or compress normal maps. There may also be an issue with how I calculate memory savings, but it should be very close to accurate. PNGs don't generate mipmaps, which is why they look odd at a distance, and also take up 30% less memory. Compressing normal maps will decrease memory usage by about 1/2 for each normalmap.

[Deltac]

Not sure if this is a bug, or just side affect from the memory reduction, but here goes!

Installed the Aggressive version as is, worked like a charm in memory reduction. Looked at some of my parts, and the textures look like they lost more than just size. The textures in question are from the FASA pack. Everything else seems fine, but Novapunch parts might be affected, too.

Pictures it illustrate the problem:

Before aggressive

After aggressive

These two were taken at the same time of day:

Before aggressive

After aggressive

The shading seems to be affected adversely.

[gardocki]

This latest update is absolutely brilliant. All these parts and still almost 1GB of headroom:

folder = Squad/

folder = KWRocketry/

folder = B9_Aerospace/

folder = AIES_Aerospace/

folder = BeastlyScience/

folder = HexCans/

folder = KAS/

folder = Keramzit/

folder = Kethane/

folder = Klockheed_Martian/

folder = KOSMOS/

folder = KSPX/

folder = LTech/

folder = MagicSmokeIndustries/

folder = masTerTorch/

folder = ModsByTal/

folder = NearFuture/

folder = NothkeSerCom/

folder = ProceduralDynamics/

folder = RBI/

folder = SCANsat/parts/

folder = StretchyTanks/

folder = SurfaceLights/

folder = TarsierSpaceTech/

folder = WarpPlugin/

[rbray89]

Not sure if this is a bug, or just side affect from the memory reduction, but here goes!

Installed the Aggressive version as is, worked like a charm in memory reduction. Looked at some of my parts, and the textures look like they lost more than just size. The textures in question are from the FASA pack. Everything else seems fine, but Novapunch parts might be affected, too.

Pictures it illustrate the problem:

Before aggressive

After aggressive

These two were taken at the same time of day:

Before aggressive

After aggressive

The shading seems to be affected adversely.

I assume you altered the config to add those folders in? If you open up KSP.log, you'll find lots of errors regarding normal maps can't be created due to unreadable textures. Simply add all those textures into the normalmap list in the config. Shading will be restored.

[Deltac]

I assume you altered the config to add those folders in? If you open up KSP.log, you'll find lots of errors regarding normal maps can't be created due to unreadable textures. Simply add all those textures into the normalmap list in the config. Shading will be restored.

"Installed the Aggressive version as is"

That means I didn't add the folder to the config.

The strange thing is when I loaded up KSP with the Aggressive version, some textures that were broken before were now fixed. Mostly parts with .png textures are affected, but a few .png textures are not affected. .tga parts appear to be unaffected, if I remember correctly.

[rbray89]

hmmm... I'm not sure the origin of the problem then.

[Argelle]

Could some nice Kerbalist point me to the direction of this log you refering to? I use window monitor to follow memory consumption but a log would be more accurate.

[Raptor831]

Could some nice Kerbalist point me to the direction of this log you refering to? I use window monitor to follow memory consumption but a log would be more accurate.

The log, I believe, is usually in your KSP root folder (KSP_osx/ or KSP_win/). Should be called something like ksp.log. I'm on a Mac, so it may be a bit different on Windows.

[team.leit]

The log, I believe, is usually in your KSP root folder (KSP_osx/ or KSP_win/). Should be called something like ksp.log. I'm on a Mac, so it may be a bit different on Windows.

I can confirm that the KSP.log is in the folder that you stuck KSP into on windows. I hope that made sense

[Amazingteknique]

Just started playing around with the new version, seems to work great I have a quick question regarding the errors with certain textures. I get the Unity Exception: Not Readable, so I copy the texture it gives me into the leave readable part of the texture compressor config. It should stop throwing that error on load ? or am I doing something wrong.

[rbray89]

s

Just started playing around with the new version, seems to work great I have a quick question regarding the errors with certain textures. I get the Unity Exception: Not Readable, so I copy the texture it gives me into the leave readable part of the texture compressor config. It should stop throwing that error on load ? or am I doing something wrong.

if it is a normal map, it should be put in the normal map list. Otherwise you are correct.

[ultrasquid]

Not sure if this is a bug, or just side affect from the memory reduction, but here goes!

Installed the Aggressive version as is, worked like a charm in memory reduction. Looked at some of my parts, and the textures look like they lost more than just size. The textures in question are from the FASA pack. Everything else seems fine, but Novapunch parts might be affected, too.

Pictures it illustrate the problem:

Before aggressive

After aggressive

These two were taken at the same time of day:

Before aggressive

After aggressive

The shading seems to be affected adversely.

I've experienced the same problem you show with FASA (and also with a few Firespitter parts). It's like they're reflecting illumination in a rotated orientation somehow. That may have confused the issue more since I'm not sure of the right technical words to use but it's very obvious when you see it.