One day I played with Lyra before migrating the characters into another file. When I did so, I hadn’t gained the experience yet to understand that I wouldn’t have dumped the onboarded memory already. UE crashed while migrating the files.
Now, UE won’t migrate any files but those (which it has migrated successfully since then.) I just get an error that there is no hero, which I tell you fully because its a gem.
I have tried deleting my destination file and recreating it. I have deleted everything in my vault cache and moved it to another drive. I have uninstalled UE5 and reinstalled it. I’m guessing that the files are at another chokepoint, perhaps in the transfer folder that I once had to move because my primary harddrive was too small? What can I do?
Hey there @MozayIC! So for one thing, migrating almost anything out of Lyra is always going to be hard to do just because every piece of Lyra touches something custom for it. Lyra even derives from a custom lyra character setup which makes it harder to get them rolling outside of the main project. Not including that most of their systems use GAS and all that jazz. If building with anything Lyra it’s usually best to start with the Lyra project first.
But on to the meat of this, what happens when you attempt to migrate anything else? Does it show any form of error or just silently fails? Is there anything in the logs/console at the time? That might point us to where things are getting held up. With the information thus far it sounds like the files are getting caught up in an intermediary temp folder location before fully moving, but I’ve never looked into it myself.
I have a file I setup just to migrate assets from after the crash. When I try to migrate from that file, I get the crash. I’ve reinstalled Unreal and I get the crash. It references the hero folder from Lyra and says it cannot be found. Only when migrating from Lyra again can I get my desired result. That’s been what I get when testing the bug.
Hey there @MozayIC! Sorry about that, been a wild week to say the least. I haven’t been able to find a solid plan of action for this one thus far. Going to see if I can get more specialized eyes on it. Can you force it to fail again and grab the exact error? I think we’re correct on what’s happening there, but to be safe (and clear to others) I’ll have that to refer to.
Okay. So, before I did that, I thought I’d want to take some drastic measures, and thats what I did. I manually deleted my Epic games folder and unreal engine installs and reinstalled them. So sorry, but I cannot reproduce the issue because I fixed it instead.
Awesome, I was thinking it was going to be a folder in AppData/local or locallow or something, but it must have been an engine folder. Regardless it’s good that you figured it out! In the future I might be able to pinpoint which folder it hides in, but I think your original assessment was correct.