Upgrade Engine - Blueprints disappeared but still visible in Content Browser

I’m trying to Upgrade the Major Engine Version from 4.27 to 5.0EA.
I have some UserWidgets. Unfortunately, they simply disappear in the Content Browser after the Upgrade.
In the Explorer they are still visible, and they have also their initial full file size.

Things I’ve tried:

  • Using a new blank project for both 4.27 and 5.0
  • Delete Binaries & Intermediate
  • Recompile C++ completely
  • Trying to migrate using two Projects one 4.27 and one 5.0 (the Migrate Option in Project)
    It stated the migrate is sucessfull, but still not accessible.
  • Fix Up redirects
  • I also can’t migrate them backwards from 4.27 to 4.26
  • I was able to force it to show up, but than I get a Load Error with no message

Nothing worked.
There is no Error Log or anything, it’s simply gone.
Any help is much appreciated.

Botched upgrade.
Only solution is to roll back.

That’s either by using a backup, or by creating a project of the old version, copying the content folder open, verify it opens, and (after making a copy) convert again.

As a general rule of thumb you should never “upgrade” in place. Always copy.
Because this happens about 1 out of 10 times you upgrade…

Hello
Thanks a lot for your answer. Its not about data loss or anything. Its alway a copy of course.
But every attempt I made led to this result. To question is, how can I bringt my Widgets from 4.27 to 5.0, or even from 4.27 to 4.26. As I wrote, I even made complety blank projects only with this content, but still I can’t bringt them to any other version.

It is a known problem. Currently it is not guaranteed to work when upgrading from 4.27 to 5 alpha, only upgrades from 4.26 are supported. (see the suiting blog entry)

I’m also not able to upgrade because I ignored the blog entry and updated to 4.26 a litzle to early but I suppose that there will ve the possibility in the next ue5 alpha release.

Make sure not to use ue5 alpha as productive system. You won’t get data back to ue4 later on.

1 Like

Thanks @HAF-Blade, your absolutely right and its also written very clearly.
I’ve only read that it will be compatible and thought it already is.