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.
- Cost: What is the cost? Is one a lot more expensive than the other? What is their licensing model?
- Support: What are the levels of support? If you have a cert-blocking bug in the engine, can you get someone to help right away?
- Ecosystem: Is your team familiar with any of the engines? How do their ecosystems compare? Can you easily hire folks with experience with these engines? Are there existing services that already have plugins for these engines?
- Documentation: How about their documentation? Are there courses or (applicable) reference projects available?
- Key features: Do any of them have any special features that would stand out? Are any missing key features that would require implementation?
- Code: Can you get the source code? How easily can they be extended and automated?
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:
- Does the internal one have any particularly unique features not present in commercial engines?
- Is it missing features that are now commonplace?
- Doing the math, how does the cost (usually more people to build and maintain an internal engine) compare to commercial engine licensing costs?
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