Comment on Report: Unity continues mass layoffs with 'abrupt' communications and 5am emails
hisao@ani.social 1 week agoArguing about UE5 feels just as bloated and convoluted as using the engine itself! Sorry, I couldn’t resist 😅
If a slow startup of the editor the first time
By “one-time learning cost” I meant that to learn how to do a thing in UE5 you will have to spend 95% of time learning things you won’t ever need to understand that 5% that you actually want. Yes, it’s also a one-time cost, but it’s not one-time cost most developers want to pay unless they really need all that compexity.
It is a philosophical difference.
It’s a personal productivity difference. If you are able to allocate N hours to make a game and you don’t need most of those features, you will be much more likely to finish that game in time in a simpler engine.
NuXCOM_90Percent@lemmy.zip 1 week ago
That is learning anything that isn’t just “ChatGPT, how do I do X?”. Also, once you learn how to use blueprints you know how to do basically anything a hobbyist game dev would want.
Which is not dissimilar to Unity or Godot. You learn the basic concepts and then it is mostly a matter of experimenting or looking up how to do isometric camera angles or whatever.
But honestly? it sounds like you don’t want a game engine. You want a framework. In that case, RPG Maker is great for making a top down square style JRPG. Unreal is great for an FPS. And so forth.
hisao@ani.social 1 week ago
Don’t underestimate what hobbyists want in their games. It’s actually AAA games that don’t want to risk and do fairly standard stuff while indies/hobbyists like to experiment and implement unorthodox mechanics and visuals. I think that, for example, writing your own 3rd person character controller (with stuff like snappy raw input movement, walljumps and also properly handling moving/rotating platforms) and cartoonish NPR rendering requires going through a lot more irrelevant systems in UE5 than doing the same in many other engines including Unity, Godot, and UPBGE. In Unity there actually is a similar kind of bloat (like URP), but it’s optional and you can just hack “good old” built-in render pipeline (also has tons of ready-to-use snippets and shaders open-sourced by community through years). In other words for me UE5 vs other engines is more like Java EE vs Python (or NodeJS) than Java EE vs Wordpress. UE5’s complexity is more of too many abstraction layers and lengthy workflows rather than being too low-level and flexible. Lightweight and flexible engines are great for hobbyists, game constructors are fine too for those who really want something very basic.