[Deleting textures] Doesn't work?

[MelvinB]

While working on my CTF-level (construction theme styled), i have alot of custom-made textures i'm gonna use, but also a few textures i want to get rid of. They doesn't fit the theme well enough.

So, i opened my texture-pack and ''right-click-> Delete'' the texture i want to delete, but i receive an error that the texture is in use, which is actually not. I'm 100% sure about that. So i can't delete the textures. I've tried also ''Delete With References'', but i'm getting the same error again. Renaming the textures doesn't work neither.

So how can i remove these textures?

[SmokeRingHalo]

While working on my CTF-level (construction theme styled), i have alot of custom-made textures i'm gonna use, but also a few textures i want to get rid of. They doesn't fit the theme well enough.

So, i opened my texture-pack and ''right-click-> Delete'' the texture i want to delete, but i receive an error that the texture is in use, which is actually not. I'm 100% sure about that. So i can't delete the textures. I've tried also ''Delete With References'', but i'm getting the same error again. Renaming the textures doesn't work neither.

So how can i remove these textures?

They ARE in use memory wise. Preform a build and the editor will delete all the textures you haven't used in your level automatically.

[MelvinB]

They ARE in use memory wise. Preform a build and the editor will delete all the textures you haven't used in your level automatically.

I did a full rebuild, but no textures have been deleted automatically. Maybe because my texture-pack is a ''stand-alone'' and not the ''call it dm-yourlevel''-stuff.

Can't manually remove the textures after a rebuild tho.

[jansoft88]

same thing happened to me with a custom static mesh. For some reason I can't delete it from my package. I tried making a new map. Restarting the editor and then restarting the computer but it will still give me an error saying that it's in use.

[ShadeMistress]

anything that isn't used will be removed when the map is saved, just close the editor, or make a new map (just to close the open one), then re-load your map, and all unused meshes, textures, etc. will be removed from the map... until then, it keeps them all in memory just in case you had decided to use them later. After closing the map, it just assumes you didn't want them and dumps them.

Same thing when cooking, it will omit anything that isn't used and only cooks the things that are relevant to your map.

[DGUnreal]

External Packages hold everything in them and do not cull out like content in your map file. So saving your map will have no effect on the external package contents.
You should not be using an external package anyway, there is no good reason to unless you are creating a mod or total-conversion.
So I would rename all of the content into the map file as the method of fixing it.

However, to fix up the package you have a few choices depending on what you have already done previously. If you have used some of the content before in the map, did any renames and other general swapping around, there may still be references to the old unused content because of the new method of asset redirection.
You can start the editor and open the package while not opening the map, so that you can delete things as they will not be in use, assuming the textures are not also applied into materials in the package.
However, if your map then has any references to these deleted objects, your map will fail to load.
There is a command "fixupredirects'" you can run that cleans redirected references but I am not at my usual PC to look it up for any options etc.

[MelvinB]

Well, the reason why i have it as an external package right now, is because i have plans to use the same content (so it's theme) for a future DM-map.

What if i change the external package to a ''CTF-yourlevelname''-package and i want to re-use the textures for an other map? Is this way causing any problems then?

Thanks for your reply's guys, i really appreciate it.

[DGUnreal]

The issue with this is that if you mess with the content of the external package to add additional assets or change some for the future map, you will probably break the package and it won't work with your old map anymore, so anyone who installs your new map and overwrites the package, the old map will no longer run.