• 0 Posts
  • 7 Comments
Joined 5 months ago
cake
Cake day: September 2nd, 2024

help-circle
  • 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.


  • Arguing 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.


  • one time cost

    Maybe stuff like shaders compiling isn’t a big deal in the long run, but one-time cost in terms of learning may be too much. If you’re going to use 5% of its features, having to go through the rest 95% when learning how to do things is a big distraction and productivity killer. Also, there is a surge of AAA games made in UE5 that have critical performance issues that developers struggle to fix for extended periods of time after release, killing performance even on the most top-notch hardware that most gamers could never afford.

    an indicator that you probably shouldn’t be developing medium fidelity 3d games on a potato

    Why though? Just use other engine and you’re good.

    For “hobbyist” 3d games, Unity is still the king.

    I’m doing a hobbyist 3d game and I’m using UPBGE. It’s terrible in a lot of ways, depsgraph kills performance, but it’s very convenient to just hit P and play during 3d modelling of the scene. This is what I would call an engine for “hobbyist”. Unity is a decent engine for professionals, for indies, for AAA, for AA, for a lot of things. At least, technically it’s there. Its management is a big issue though.