I’m new to unreal engine but every time I tried to start a new project, after a while when trying to open the project again, it would throw similar errors (picture below) and would take away the first person character from the game.
I tried moving to a new project at first as I only started so it didn’t really matter but after a while working on my project it seems to happen again and I don’t know what to do… I tried searching for other posts on the subjects but I didn’t really understand their solution for the subject (most of them were in c++ while I work in blueprint and the rest focused on specific assets the user brought while these ones are ones the unreal engine provided me).
Idk why a project would work perfectly one day, even after closing and opening it. And in another day the same project I didn’t touch would crash…
I Tried moving the content of the project to another project and it still did not work.
Hey there @Yuval63! Welcome to the community! So I’ve had this issue after having to force delete an asset that was dug in more than expected. This could be due to redirectors or caching.
Try a couple of the fixes in these threads and let me know if any of them work out! Disclaimer: Please back up anything you’re going to delete out of the caching folders before you do anything. Some fixes are a little more intrusive than others!
I tried going over all 23 comments. Sadly none of the solutions presented in the comments worked (sadly, out of the 23 comments only 2 were really solutions, the rest were either cpp related solutions which are irrelevant since I’m using blue prints or more requests for help)
They are still in the folder itself but in unreal engine the class of “FirstPersonCharacter” Seems to not exist… (The class where all the resources come from)
In the pictures bellow you can see that in the content folder itself the class “FirstPersonCharacter” exists but in unreal engine it does not. (I tried to import it but since it’s technically inside the engine, it just doesn’t show the blueprint)
Hmmm, this is a bit of a tough one then. It’s acting like it would if you say imported an FPS template on top of one after deleting the original reference. Alright let’s try 2 more things.
This one is definitely not going to work, but we have to say we tried it! Go through your project and for each folder that contains uassets (or contained) fix the redirectors.
This is tedious but if you’re a bit more command savvy you can fix all redirectors in the project at once if you can launch the project from cmd and know how to add arguments UE4Editor.exe <GameName or uproject> -run=ResavePackages -fixupredirects More info over on the docs. - Redirector Docs here: Redirectors | Unreal Engine 4.27 Documentation
Second: Move the Uasset to a backup folder, launch UE, let it get angry, fix redirectors like above and toss any references that come up as errors if possible. Save then try to reimport it again fresh and let me know if the console prints anything relevant during.
For the first method. I hope I did it well. Going through all the folders using ue4 and choosing fix up redirector. If so, then sadly it didn’t work.
As for the second method, something weird happened. I moved all the content files to a backup file on my desktop. In order to make sure it’s not even in the ue4 folder for it to find. And even though it doesn’t have the firstpersonbp - blueprint, it still complains about the problem… I even tried to take away the FirstPersonExampleMap_BuiltData from the maps and yet it still complains about it…
It’s a bit of a different warning in term of the place it complains about but the overall problem is the same… Maybe I did not understand correctly what to do or the problem lies in something else…?
Alright, so in that case I’m out of the usual subjects that fix issues finding resources internally. I’m going to have to do a bit more research on the Outer metadata it’s looking for and see if there’s any way to make sure it’s directed to where it needs to be.
The engine is a massive undertaking with so many hands touching it every update, that sometimes things can slip through. At the end of the day we’re working with so many separate systems in so many different ways that when you find an edge case, it’s entirely possible you’re one of the few people in the world that have the exact scenario.
I hope the project itself wasn’t too far along so if this is a permanent roadblock you can just migrate the stuff that survived in the worst case if I can’t find anything. I’m still banking on the fact that the community might have someone who knows this issue and can get this sorted for you, but the odds are slim since the usual fixes didn’t work.