Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
But it still looks amazing..
That is not true quite a few games out there use CryEngine.
Despite its age, the world looks fantastic
The team chose to focus on content/story over shipping on new engine which is actually a mammoth task that requires you split focus - half the team trying to build the world and the other half working around limitations, bugs, customising, etc....
They made a good choice.
Not so.
Since UE5 was already available when development started, the idea that switching to it would have been a "mammoth task" that split the team’s focus doesn’t really hold up. The main reason studios avoid changing engines mid-development is the huge effort needed to transfer assets, tools, and workflows—but if UE5 was an option from the beginning, there wouldn’t have been any migration; they could have just used it from the start. That means any struggles with an outdated engine were self-inflicted, not an unavoidable challenge. Plus, UE5 actually makes development easier in many ways, with features like Nanite, Lumen, and World Partition reducing the need for tedious optimization and workarounds.
The argument that switching engines would have "split focus" ignores the fact that sticking with an old engine does the exact same thing, because developers end up wasting time fighting its limitations, fixing bugs, and customizing outdated tech. Either way, the team would have had to divide their attention—the difference is that using UE5 from the start would have set them up for fewer technical hurdles in the long run. There might have been valid reasons for avoiding UE5, like it being in early access at the time or the studio having a lot invested in their old engine, but the idea that it would have made development harder just doesn’t make sense, since using outdated tech likely created just as many, if not more, problems.
That's a bit picky though, the game looks very good.
And this is exactly why we're stuck with mediocre graphics—because of comments like this that validate visuals which were outperformed by current technology over five years ago. I think the real issue is that I’m talking to a group of people who are two to three generations behind in tech, so these visuals seem impressive to them because they’re still living in the past.