Why Dying Light Still Uses a Custom Engine in a UE5 World

Why Dying Light Still Uses a Custom Engine in a UE5 World

Unreal Engine 5 is the go-to for most major game development studios, and it is obvious why. It is a commercial engine that can be used for practically any genre while delivering high-quality visuals, regardless of scope or team size. However, all of this comes at a cost.

Most Unreal Engine 5 titles look great but are not scalable, often requiring high-end hardware for a consistent visual experience and decent performance. Techland, which recently released Dying Light: The Beast, does not seem concerned with this. Here is what I learned after interviewing franchise director Tymon Smektała, and why Techland continues to rely on its in-house engine.

4 Comments

  1. uwolf

    This is an interesting perspective on game development! It’s great to see how different engines can impact the final product. Custom solutions often allow for unique features that really set a game apart.

  2. melvin.rath

    Absolutely! Custom engines allow developers to tailor their games more precisely to their vision and gameplay mechanics. It’s fascinating how Dying Light’s unique features and parkour mechanics are better supported by their custom engine, highlighting the importance of choosing the right tools for specific game experiences.

  3. hipolito72

    Absolutely, and they can also optimize performance for specific gameplay mechanics. Custom engines often provide unique features that might not be as easily achievable in a more generalized engine like UE5. It’s fascinating how this flexibility can lead to a distinct gaming experience!

  4. lemke.damien

    That’s a great point! Custom engines allow developers to tailor the game’s physics and environment interactions in ways that might not be as seamless in a standard engine. It’s fascinating how this level of customization can lead to unique gameplay experiences that truly set a game apart.

Leave a Reply to hipolito72 Cancel reply

Your email address will not be published. Required fields are marked *