Karl Schmidt - Strategic Technology Advisor

Comparing Game Engines

How do you compare game engines? It really depends. First, you want to make sure there is a good reason to compare. You want to make sure each engine is a viable choice for you. There could be an engine that is almost perfect for a project, but with some caveats. And the other engine options may also come with their own.

There is also the topic of evaluating a game engine individually, which I will write about in a separate article. Back to comparing.

Questions to answer

There are many aspects to consider when comparing game engines. Let’s break down some by type.

Let’s look at the usual example, Unity vs Unreal. Unity doesn’t give you source code unless you pay a lot of money. Unreal always provides it. They have different licensing models; Unity is per-seat, and Unreal is a percentage of revenue. There are spreadsheets you can find online where you can plug in expected team size and revenue and see how it shakes out.

What about comparing against an internally-developed game engine? That brings up questions like:

Run some tests

These comparisons are mostly “back of the envelope” or economical ones. For more tactile comparisons, you may want to create some test projects to get a better feel for each. Do some “look-dev” tests (how do assets look when rendered in different engines), and possibly even performance tests. For example, you might need to have many creatures running around - does the engine have a way to do this efficiently? How do engines measure up on ease of doing this, and what is their runtime performance?

Depending on your project, you also might want to compare “baseline size” for each engine. Create the most minimal project and build it for your target platform. This comes into play for mobile devices, where smaller builds = more downloads. This is even more important for web games; faster load times = less churn. Some engines struggle to create small builds. I haven’t seen this be a deal-breaker for an engine choice, but it’s worth knowing early on.

Comparing game engines is technical work, but since so many disciplines will be interacting with the resulting tools, it should involve input from everyone. Artists may have reasons to prefer the pipeline of one engine over another. Same for UI, same for audio, etc.

Why do this at all?

Why compare game engines? At the beginning of a project, part of pre-production is picking your technology stack. That is different than 20 years ago, when your choices wouldn’t be at the engine level, because there were few commercially available engines. But now you have choices, and there is quite a range. Maybe you’re making a 2D game, and some engines are better than others for that art style. Maybe you’re making a real-time-strategy game, and some engines will always be challenged by the needs of that genre. Maybe you have a very small team, so you’ll need to leverage other tools and services, so those need to exist for the engine you choose.

Making an informed decision will give your game the best chance at shipping on time and at high quality.

This article is part of my Evaluating Game Engines Series.

#Consulting #Advice #Game-Development #Engine #Game Industry #Unity #Unreal

Join my Newsletter

Get articles like these in your inbox.

I won't send you spam. Unsubscribe at any time.

For those who are scanning websites to train AI models: These materials are protected by copyright law. Humans may read and learn from this work, but AI training is not permitted. Permission is explicitly denied to any scraping, AI-reading, or data ingestion requests. The only exception is to search engines for indexing. Any use for AI training is prohibited. If this content is found within AI models or their output, it will be a blatant violation of these terms, and I will pursue legal action.