Deleted Assets still in file folder

Hi, not sure if it is intended, but if I delete assets in the editor, their .uasset files still exist in the file system with a size of 1kb.

Hi anteevy,

Thank you for your feedback, this is a known issue that we are investigating to find a potential fix. Have a great day!

I was trying to replace an “existing” asset with a new one and it kept complaining. I exited the program, deleted the file, and when I got back in, it worked fine. I have others I’m thinking of deleting. I was hoping to find out if there was a potential issue or not.

Good to know it’s a known issue, I am also experiencing this.

We’re seeing the same on our project too. Is there any estimate on when a possible fix is coming?

Unfortunately I currently do not have a good timeframe on this. Thank you for your continued patience while we try to work out a suitable fix.

I hope this gets fixed asap, thank you !!!

Having the issue just that we have them there: 1kb Files in Content Folders - Feedback & Requests - Epic Developer Community Forums

This still hasn’t been fixed, after renaming asset it is impossible to rename it back due to existing asset (in explorer, not visible in content browser)

It’s simply because “we are investigating” phrase doesn’t actually mean that anyone is really investigating.

Hi everyone,

I just checked in 4.6 and, after naming an asset and then renaming an asset, when I renamed the asset back to the original name I was unable to reproduce this error on my end. I could not reproduce it by deleting the asset and then creating a new asset with the same name, either. Do you have any reproduction steps that I can take to recreate this error?

Hi

We are experiencing a very simple issue with assets files (4.6). If we create an asset, and then rename it, the old asset file still sits in the folder. So we are having two asset files: the new one that works like it’s supossed to, and the old one, not seen by the editor, but still there in the folder. Not a huge problem for small projects but later on this kind of garbage files can be a bit annoying.

Hi rimau,

I believe you are running into redirectors, which is expected behavior. Have a look at this page and try the “fixupredirects” command to see if it clears up the error. Note: Depending on the size of your project, this may take some time to fully run.

Thanks for the response. I do understand what to do now. But could you please elaborate why? :slight_smile: What is the reason behind it. Is it just consequence of some other functionality of the engine, or is there anything deeper to understand that can be used to an advantage?

Hi rimau,

The redirectors are in place to prevent asset breaks when referenced from other objects in the editor. We are working on additional solutions to immediately update reference filepaths but currently the redirectors serve as a way to continue without breaking references when moving/renaming objects.