Comparing Enums in UE5 got worse?

What’s going on here?

Seriously, Epic sabotaged blueprint users? Why?

Btw, it’s still rather crappy that only the equal has a “proper” enum node for this…

bild

Yep… Seems like intentional sabotage. Very difficult to fix by making you use an extra node.
Oh, the humanity!!

Disable this:

image

I hope it’ll be helpful for you.

My Products

You logged in for the first time in 2 years to post that? Ok…

Thank you! I wonder what other side-effects that will have… guess we’ll see!

Still, nobody from Epic will ever read this, but I have to reflect that the threshold for beginners to wanting to use Unreal seems to be raised with every release. It’s not a good trend.

confirmed still broken in 5.3, have to uncheck that box just to do greater then compare on enums

Ever find out what the side effects are?

Still broken in 5.4.4