How can UE5 games be in development when Epic advises us to not use it

If UE5.0.1 is an early access build, and Epic advises us not to use it for active development, then why are so many games getting announced that ‘use UE5’. Are these games actually being built in UE 4.27 to be updated when UE5 launches? UE5 is full of bugs right now and a few weeks ago I switched my game to develop in UE5. Now I’m hitting these devastating bugs and optimisation issues and considering going back to 4.27 and redoing lots of development there. There seems to be no answer to this as on one hand UE5 marketing is pushing that it’s here and games are coming, but internally we shouldn’t actually use it. As a developer I really would appreciate some clarification. And should I ignore these bugs for now and carry on development in UE5

Thanks

I guess that big companies use customized versions of the engine, and they probably have programmers whose job is to fix these kind of bugs.

The Witcher 4 should use UE5, and I heard that even EA is probably gonna adopt it (instead of their proprietary Frostbite), probably it’s also more convenient for them to fix bugs in Unreal than mantaining improving their own engines :sweat_smile:

I think that’s really hard for an indie developer to publish something with UE5, I’ve had so many problems with it that I love and hate it alternately.
And I wasn’t taking about performances: sometimes I struggle reaching 30fps with a 5950X and a 3080ti, I don’t want to imagine how it is to develop with a notebook…

1 Like