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

[Green Skull]

Hmm, smunisto. I had a similar problem last week, where I updated several things at the same time, and it broke ATM. I never figured out exactly what it was though, no matter what I removed or reverted I couldn't fix it. I ended up having to destroy (uninstall) KSP completely and start over with a clean re-install.

Exactly the same happened to me a couple of weeks ago. I feel this is a KSP problem in general with the 0.23.5 version. Had the same version of 0.23 for months, modded the hell out of it and it still works perfectly, upgrade to 0.23.5 and it really started messing up after a couple of weeks. What I did was copy the entire Game Data folder to desktop, put KSP folder in bin, re-install from my mirror, remove old squad / nasa parts from copied game data, merged both Game Data folders and still works perfectly now... When this game copy dies I'll do the same again...

[PolecatEZ]

Just try basic ATM version for now with a clean install if you can. Near as I can figure, once its broke its BROKE.

I reinstalled (total wipe) KSP.

Added in Kethane, RPM, Scansat, Vesselview, B9, Firespitter, and Mechjeb all at once. Good load.

Added in D12 Knockout pack, overwriting everything. Good load.

Added in ATM (Basic). Did the normal delay thing, then good load.

Copied over it with ATM (Aggressive) and added the custom config. All loaded fine.

There might be something to breaking saves if a load is bad, as when I was troubleshooting I literally removed everything in GameData and the game loaded fine when it was totally empty, but was still broken the second I added anything back in to the empty GameData folder. I was hunting everywhere for some kind of cache file I might have missed because nothing made sense, but didn't think to delete the save game folder (doh!).

[Virtualgenius]

Funny you should say that Green skull same thing happened to me so i copied gamedata out minus nasa and squad folders, deleted it through steam download new version copied gamedata back in work perfectly

[Green Skull]

The method I suggested should fix some random game breaks but I agree with Polecat that in his instance when it's broke its frakked Back OT can I add that config to mine?

[PolecatEZ]

Yes you can, but since there's still a lot more to add later you can hold off for now.

[smunisto]

Ok. Testing - all tests are done with D12 Knockout version installed + Polecat's cfg from ATM, which means the replacements from D12 have been applied to the Squad folder in my broken install.

TEST 1

1. I made a clean install;

2. Moved the stock Squad and Nasa Pack folders out from GameData and into a backup location out of this KSP install;

3. Copied the whole Game Data folder from my broken install to the new one. ALL of it, yes. Even its Squad and Nasa Parts folders.

4. Did not copy over the saves from my broken install.

Result: ATM does not work = Game runs out of memory.

TEST 2

1. I made a clean install;

2. Copied the Game Data folder from my broken install to the new one, without the Squad and NASA folders.

Result: ATM works perfectly fine = Game runs with all my mods, just without saves.

TEST 2.1

3. I copied over a full Knockout version on top of this game folder.

Result: ATM does not work.

---------------

Seems like the game breaks when D12 modifies the Squad folder, I don't see any other reason.

Tomorrow I will try to install the old version of D12, without knockout, and I will try bringing back my saves from the old broken install to test it too.

I don't know what more to do.

---------------

EDIT 1:

I have managed to confirm that what breaks ATM is something that the D12 Knockout version does to the Squad folder.

This is easy to reproduce and I can upload my whole install somewhere. I don't know if it's related to my HW configuration in some twisted evil way, if it is related to the two mods not working well with each other for me, or with fault in the cfg's of just one of the mods.

However I am able to reproduce the issue 100% of the time and I am sure that the it is not KSP itself, as I have tested all of the bug reproductions on 2 identical clean installs

of the game.

Each of the 2 installs stops ATM from working when I install D12 Knockout and it replaces files in the Squad folder, and ATM starts working immediately after I replace the Squad and NASA mission folders with the stock clean install backups I have and delete the Knockout folder(I am not sure about this second thing, I just do it as a precaution) in the Xpansions D12 folder.

Maybe you guys need a chat, maybe you need to check the output_logs again. I don't know. I will try to bring my old saves, but at this point I am sure it's D12 that's breaking ATM, not KSP bugging out and breaking.

EDIT 2:

Brought my saves from the "broken" install too. They work flawlessly. So the issue is between ATM and D12 Knockout.

Edited May 1, 2014 by smunisto

[PolecatEZ]

I'd say just try the D12 Supplemental version then, should be no conflicts at all as they're just simple parts that way. Also, are you using ATM Aggressive or ATM Basic?

I think I'm just going to go back to the drawing board with how knockouts work, but there really aren't any great solutions. The safest one is just to give a list of folders for the user and say "Erase what you can."

[smunisto]

Sorry Polecat, didn't mean to give you a headache.

I think I will stick with the new parts without Knockout or Supplemental, because I've got procedural wings and enough Mk2 and Mk1 fuselages in the B9 style.

I hope you fix the thing that is breaking knockout soon.

I wanted to post in your D12 thread, but I will hijack this thread - Could you please make a screenshot-catalog-thingy with all of the parts for each version. It will help with choosing. Just like with your preview now, but all of the parts, wings, lala, all of these.

[sebi.zzr]

I'd say just try the D12 Supplemental version then, should be no conflicts at all as they're just simple parts that way. Also, are you using ATM Aggressive or ATM Basic?

I think I'm just going to go back to the drawing board with how knockouts work, but there really aren't any great solutions. The safest one is just to give a list of folders for the user and say "Erase what you can."

ATM is not working with knockout because,D12 has empty *.cfg for squad parts that are replaced!It has nothing to do with ATM versions.

[Smorfty]

I've sat here for 6 hours to pinpoint this problem I have.

I've found a silly clash of three addons that lower my fps by 20.

It's when you have ATM, MechJeb and the 000_Toolbar addon installed at the same time.

Take out one of them and my fps goes back to normal.

To experiment, I made a clean install of the game. Then I installed (clean) versions of ATM, MJ and the Toolbar and I was able to recreate the fps loss. If I remove one of those addons and run the game with the other two, the game runs just fine again.

I even tried using older versions of all three addons but no cigar.

I think the problem is that MJ creates a whole lot of icons for the Toolbar based on all your custom windows. It seems to do this way too often. For example if you change the name of one of your custom windows. MJ will create Toolbar icons every time you press a key to enter the new name of your custom window. Leaving you with a lot of nonsense icons with names like "Orbit I", "Orbit In", "Orbit Inf", "Orbit Info", etc.

I think that every time it does, Active Texture Management goes in and does something that creates cpu spikes because of some "new" button texture being added.

And before you ask:

- I'm using the latest version of all of the addons I talked about.

- I've experimented with this in a completely clean version of KSP. With completely stock/default addon settings.

Edited May 4, 2014 by Smorfty

[Casen]

I have a quick question about how this works.

My game data folder is currently 2.49 GB.

I have the 3-1 aggressive ATM installed.

When I load KSP it freezes at the beginning, usually on the first part (this is normal I know).

Is this when the ATM loads/resizes all the parts?

I only ask because I watch my task managers memory for KSP go from 0-2,000,000K while the game is frozen.

Then, once it un freezes, and actually starts loading all the rest of the parts in, it will increase to 3.5GB at the loading screen.

It seems like its loading the reduced textures and then the full size ones too... Or am I thinking about this the wrong way?

[LameLefty]

I may be missing something as well; in prior "2-nnn" versions, my KSP.log would show several hundred megabytes saved. Now, with 3-1 Aggressive installed, it showed 2MB (yes, 2 megabytes) saved.

[rbray89]

I may be missing something as well; in prior "2-nnn" versions, my KSP.log would show several hundred megabytes saved. Now, with 3-1 Aggressive installed, it showed 2MB (yes, 2 megabytes) saved.

the calculations are just wrong. I forgot to tie them in.

[rbray89]

I have a quick question about how this works.

My game data folder is currently 2.49 GB.

I have the 3-1 aggressive ATM installed.

When I load KSP it freezes at the beginning, usually on the first part (this is normal I know).

Is this when the ATM loads/resizes all the parts?

I only ask because I watch my task managers memory for KSP go from 0-2,000,000K while the game is frozen.

Then, once it un freezes, and actually starts loading all the rest of the parts in, it will increase to 3.5GB at the loading screen.

It seems like its loading the reduced textures and then the full size ones too... Or am I thinking about this the wrong way?

The "frozen" part is when all the textures are loaded now. The additional MB is from everything else. Unmanaged textures, Assets, Planets (and their textures), and all the meshes.

[rbray89]

I've sat here for 6 hours to pinpoint this problem I have.

I've found a silly clash of three addons that lower my fps by 20.

It's when you have ATM, MechJeb and the 000_Toolbar addon installed at the same time.

Take out one of them and my fps goes back to normal.

To experiment, I made a clean install of the game. Then I installed (clean) versions of ATM, MJ and the Toolbar and I was able to recreate the fps loss. If I remove one of those addons and run the game with the other two, the game runs just fine again.

I even tried using older versions of all three addons but no cigar.

I think the problem is that MJ creates a whole lot of icons for the Toolbar based on all your custom windows. It seems to do this way too often. For example if you change the name of one of your custom windows. MJ will create Toolbar icons every time you press a key to enter the new name of your custom window. Leaving you with a lot of nonsense icons with names like "Orbit I", "Orbit In", "Orbit Inf", "Orbit Info", etc.

I think that every time it does, Active Texture Management goes in and does something that creates cpu spikes because of some "new" button texture being added.

And before you ask:

- I'm using the latest version of all of the addons I talked about.

- I've experimented with this in a completely clean version of KSP. With completely stock/default addon settings.

ATM Does nothing (absolutely nothing) after the loading screen. What is likely happening is that MJ or OOO_Toolbar are trying to read a texture that has been marked as unreadable. An exception will have to be added for it.

[benc85]

I'm getting a saving of 108MB (according to the KSP.log) which seems a bit lower than it used to be. Is that just because its not calculating it properly then?

[rbray89]

I'm getting a saving of 108MB (according to the KSP.log) which seems a bit lower than it used to be. Is that just because its not calculating it properly then?

As I just mentioned, Yes.

[biohazard15]

I've made an updated config for the latest NovaPunch test release: here.

Note that it's not completely compatible with NP 2.03.5 - normal map names for two engines changed in test release.

[MNSRSkittles]

Hi, this mod makes my Minmus look like this: http://puu.sh/8xY5A.jpg

And it's terrifying.

How can I fix this?

[rbray89]

Hi, this mod makes my Minmus look like this: http://puu.sh/8xY5A.jpg

And it's terrifying.

How can I fix this?

Umm... no it doesn't. This mod doesn't touch planet textures. It can't. You probably have your texture settings in the Graphics settings turned down.

[MNSRSkittles]

Umm... no it doesn't. This mod doesn't touch planet textures. It can't. You probably have your texture settings in the Graphics settings turned down.

The instant I remove this mod, same graphical settings and all; it looks fine.

[rbray89]

The instant I remove this mod, same graphical settings and all; it looks fine.

What are the graphics settings on?

Are you using Texture Replacer to replace the minimus texture?

Aside from that, there is no way for this mod to affect those textures, as those textures don't exist on the file-system.

[MNSRSkittles]

What are the graphics settings on?

Are you using Texture Replacer to replace the minimus texture?

Aside from that, there is no way for this mod to affect those textures, as those textures don't exist on the file-system.

So, removing and then reinstalling the mod seems to have fixed the issue.

Either that or I did a stupid then fixed said stupid, I dunno.

But great mod, increases my FPS a lot.

Sorry for being a dumb.

[Taki117]

Is there any benefit to increasing the compression beyond 4x? I upped it to 8x with no significant reduction in memory, but a significant decrease in quality. (4x had no such quality decrease)

[Faark]

Hey, does anyone else get such an exception?:

NullReferenceException: Object reference not set to an instance of an object

at ActiveTextureManagement.ActiveTextureManagement.Awake () [0x00000] in <filename unknown>:0

UnityEngine.GameObject:Internal_AddComponentWithType(Type)

UnityEngine.GameObject:AddComponent(Type)

AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup)

AddonLoader:StartAddons(Startup)

AddonLoader:OnLevelWasLoaded(Int32)output_log.txt

,

Removing my own stuff didn't change anything. So far my best guess would be someone like TextureReplacer unloading GameDatabase.TextureInfo.texture's, something my own stuff is unable to stand. But hopefully someone already knows more...

*edit* I'm not that sure anymore on what installation this was. It might have been one of the .23 installs, so probably just a version conflict. I'll write another msg in case it happens again on a recent version.

Btw, you might also want to update the source link in the first post.

Edited May 9, 2014 by Faark