Making some changes to my project and cleaning a few things up.
Alot of the current warnings im getting in my builds are from blueprint that I have removed, however when I go to select “Fix up Redirectors in Folder” nothing happens?
Hi ,
Which folder specifically are you trying to fix redirects on? Try it on the Content folder in the Content Browser, are you seeing the same problem?
HI ,
We have not heard from you in several days. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information.
Hey, I’m having this same issue, should I start a new question?
Hi paragonx9,
In this case I think it’d be best to keep the information together here. What folder are you attempting to run “Fix Up Redirectors” on? Have you tried the full Content Browser? What steps are you taking to reproduce this error on your end?
I have had this happen to me randomly over the years and just had it happen again today. I forget the ways I’ve solved it in the past (though generally doesn’t happen easily) but I believe it was a result of many restarts of the Editor trying different things (Editor restarts tend to be required to finalise actions made).
I think every time it has happened to me has been due to moving files, which happens most of the time so I tend to delete files and import fresh ones if I ever need to re-locate them (though this can be very time-consuming).
I always use ‘Fix up redirectors’ after moving files, which always comes up with a loading bar the first time to show it is cleaning things up but often it doesn’t end up removing the redirectors.
I’m not sure on exact reproduction steps (as it appears randoms) but it has happened in new projects, generally with imported meshes that have dependencies with materials and textures. I’m sure playing around with a few imported models, that have materials and textures, and moving the files around would cause it to trigger after a few attempts; renaming should help a lot too (especially if you rename before fixing redirectors) along with some Editor restarts in-between attempts.
Is there a reason why redirectors exist beyond closing the Editor? My understanding of why they exist is so as to avoid dependencies breaking while references are cached in the Editor. If that is the case, what reason is there for them to not be cleaned up automatically on Editor close/start (start to avoid incomplete clean-up on close due to a crash) without us ever having to manually deal with them?
I’ve attempted renaming my current assets affected back to what they were and then trying to fix up redirectors, combined with editor restarts, but no luck. I’ve manually gone through every folder in my content browser (which is a lot of folders) and told it to fix redirectors. The folder containing the redirectors does nothing when telling it to fix them.
I’ve found adding the files, with the exact same naming, back to the folder with the redirectors that won’t clean up seems to either resolve or overwrite their redirector; I then move the files again and it seems to clean up properly (or I re-do that approach until it does).
I am not sure what would happen if I was to do this with a dummy file of the same name but I did not want to risk breaking it so I did not try that.
Unfortunately I had renamed a bunch of files so I had to rename them back, and then rename them again after the redirectors were cleaned up properly.
Having this problem trying to rename a folder from a workshop asset, and fix up doesn’t fix them. If I filter the reference in the content browser, I can see it, but fix up does nothing and finding the asset just take me to the folder where the asset I need to replace it with is sitting, but theres no option to do anything about it.
Also, why do you people close questions when no one has bothered to answer it? Most people don’t ask a question on the forum and then repeat themselves every day until someone answers. I see you guys do this a lot so Im curious what the line of thinking is here…
Ask a question, wait for an answer. 99% of the time bumping your own question will get you banned from many places.
Anyways, what do we do when fix up directors does nothing?
Hello Old-Crow,
I was unable to reproduce this issue on my end, but I have a couple questions for you to help investigate this issue further.
- Can you reproduce this issue in a new project?
- If so, could you provide a detailed list of steps so I can reproduce this issue on our end?
- What engine version does this issue occur for you on?
Thanks!
To reproduce the issue this should work…
- Create a main folder
- Create several sub folders inside the main folder
- Add several assets to the sub folders that reference each other in some way.
- Rename main folder.
- Turn on the filter for “Show Redirectors”.
you will see all of the redirectors and in most cases you can r-click and choose to fix or delete them, but every once in a while you will come across one that says “Failed to load assest” as soon as you r-click it. you wont be able to get rid of it unless you do what furinyx said above.
Epic can not enhance the moving system as I noticed and this make work annoying and time-consuming, Example if you open a new folder under the content and moved all the folder which you created before into the new folder then the problem will start even if you Fix Up Redirectors… EPIC should fix this issue instead of everytime upgrading to a new engine version. why they do a new version anyway if they do not fix the engine issue?
I am having this same issue in 4.21. “Can’t find file for asset ________ referenced by _______”.
Said assets were named and removed long ago. Show redirectors isn’t working because even the folders they claim to be in don’t exist.
Crazy this problem still exists in 5.1, I don’t get any error messages but tried fixing one redirector and it asked me to save the level and then crashed when I tried overwriting the level.
When the editor reopened I didn’t lose anything but trying to fix the redirector this time just gave a load bar and did nothing. Eventually fixed it by moving the asset back and forth between old folder and new folder 3 times