Early Access term confusing (is this an Alpha version or just a tech demo?) and some questions related to production using UE5

Frequent updates for UE5 are expected

Be aware that the timestamp that was linked was talking about post-stable 5.0 release, not Early Access.

They explicitly addressed the Early Access version at this timestamp: https://www.youtube.com/watch?v=6W1DFdLiWN8&t=4958s

“Maybe 1 or 2 hot fixes…similar to Previews…common issues, but after that, the next release will be 5.0”

If this is an Alpha build, I feel confident to move forward. If this is a tech demo, with zero public updates for the next 8 months, I won’t be using it and will continue using UE4 until UE5 is ready and an Alpha version becomes available.

While this may be redundant, figured I’d say my two cents: I would say this is like a beta compared to other software release pipelines, not alpha (which implies really rough edges; I would say they were “alpha” when they announced UE5), but definitely not a Tech Demo.

“You might want to consider trying UE5 Early Access if most or all of the following statements apply to you”

So I wouldn’t use UE5 exclusively.

I think this is reading into the “trying” word too much. It’s more of a suggestion of “try it out and if all of the other descriptions match your case, then go for it.”

Further, in the Compatibility section they state that UE5 EA projects will be compatible with UE5.0 stable.

With that information plus the wording in the prior sections, I made the decision to use UE5 EA exclusively for my project (that is set to release well after Q2 2022). I don’t think there’s an issue here with this, as long as you’re okay with instability over the next 6-12 months.

I’m also well versed in C++ (though my project is mostly BPs), and have no issues with diving into engine code (which I do every other day, but my project is also an advanced one so that may not apply to you).

1 Like