.uassets not being recognized (same version)

Hey,

I could really use some help here. I have a project in UE5.3.2, I accidently deleted a folder containing content of a bunch of materials and a blueprint. So; I went to my autosaves, pulled out the same folder from the project I’m currently working on, in the same version of Unreal (of which I had made this BP and materials in this version of Unreal) and yet Unreal won’t read the .uassets . I’m not sure what to do, I’ve read up on some UE Forums, there seems to be inconsistent answers and I’ve tried most of them. I’ve tried moving them to different folders, even just putting all the content in the content folder itself. I’ve tried “Fixing Redirectors” I’ve also tried Validating Assets in the Folder. UE5 reads the folder, and sees that there are files in the folder. Saying: “Files Checked: 60, Passed: 60” but the .uassets won’t show up in the actual folder in Unreal. So, I’m pretty much at a loss, if anyone could help that would be great; as it is quite literally the same folder with the same assets as it was prior to deletion, so I’m not sure why it wouldn’t work in the same way.

Greetings @N.Tannoy

Welcome to the Unreal Engine Community Forum! The type of issue that you’re describing usually happens when you have assets from an older version of UE (5.3.1 etc) and are trying to use them in a newer version of UE. If you’re 100% positive it was the exact same version you had both on, I’d check and make sure you didn’t have any plugins in that build. Those are the two key contributors that produce this problem 99% of the time. That’s where I’d start. I hope that helps.

Oh, that’s unfortunate. I do have a few plugins enabled from Unreal and one from Unreal Marketplace, but they’re things like Niagara fluids, etc… and a camera plugin. Could these be affecting my .uasset problem?

It can definitely cause this. But, just because it can doesn’t always means it’s the culprit. I’d try disabling them and see if you still get the error. Let me know what you find.

It’s no worries. I ended up just redoing the work. Although, that could have most certainly been the issue. Thank you for responding!

You’re welcome! I’m glad that you were able to get the issue fix and were kind enough to post your solution. Thank you @N.Tannoy !

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.