Blueprints not showing in content browser

Hello! I’ve been developing a game with version 4.18 for about a month now. Today I was trying to do something in blueprints but decided to scratch it and thus I stashed the changes with git. After that I’ve been having problems with the editor not detecting or showing blueprints in the Content browser or in any other part but they are physically located in the correct location.

Since I’m using version control, I’ve tried reinstalling the engine with no success, the same still happens.
In the image, even though the blueprints are in the correct folder, the content browser doesn’t show the assets and for example, in the image there are three blueprints that I require for some of my levels, one being a Game mode, the other being a HUD child and another being a Player Controller, none of them Show up and I cannot find/use them inside the editor in any way.

Note that besides those three, I’m missing several UI Widgets, Enums and other blueprints. Is this something due to the engine or did I screw up in some way?

Hey there, you have 1KB files, usually those are redirectors and not meant to be recognized by the engine as assets, they just exist to avoid breaking references. I would suggest for you to start doing Right Click on Content folder and do Fix Up Redirectors. This won’t fix your problem, but it’s a way to prevent that from happenning in the future. If you can’t find the uassets (that are larger than 1kb) for the assets you are missing, then they are probably gone. Have you got an older version in git to restore?

Did you downgrade the Engine Version or switch from a custom compiled engine to a standard distribution? This may explain why your uassets are not being recognized anymore.

Once there is a discontinuity in your builds like that, you may have to rebuild from scratch. Build from a fresh project (no intermediate files) and see if that helps. Make sure to use a version that built fine before.

If you’re not sure which directories are intermediate you can “Zip up project” (from File->Package Project), extract it, and build it. If you have any external plugins (MyProject/Plugins/…) you will also need to manually copy them to the new project directory (don’t copy their intermediate folders either).

Sometimes you need to rebuild UE4 too. Don’t ask me why but it has worked in the past. Last resort tho, it takes forever. GL!

Nope, I’ve been using the same version from the standard distribution

I think this was the reason. I used to be using git LFS but at somepoint decided to remove it for some reason and I think that’s what caused the problem. Every commit using LFS has files over 1KB but every commit after that is wrong, since it has been a lot of commits It’s not worth to go back to a previous working version, I think I’ll be redoing it from scratch, maybe for better.

Did you at least try building what you want to use from scratch? You said “decided to scratch it and thus I stashed the changes with git” so I assumed you wanted to go back. You should try building whatever it is you want to keep from scratch, as problems with intermediate files happen all the time without any messing around like you have done.

Repositories are designed to prevent this so you might want to learn how to use them better. Version Control Best Practices | Tower Blog

And, BTW, if you got confused with your repository then the problem has nothing to do with redirectors. That happens when you move stuff in the editor.

The thing is that the problem is not only with what I was trying to build, ever since I stashed the changes many files were missing and unusable, including several UI Widgets, gameplay related blueprints and more. I tried creating another project, copying it, reinstalling the engine, going back several commits, etc. None of those options worked and I think it’s due to me messing up the VCS with adding and removing LFS without really thinking, but I’ve worked a lot on the project ever since so it’s not worth to restore to a previous working version since that was like at the beginning of the project.

A tip i can give you is after you use the Fix Up Redirectors, use a program like File Seek that allows you to search fast for files that are under 1 kb and delete them if you are certain they are old. That way you don’t send these files to the git repository.