Why Split Fiction Chose Unreal Engine 5

Resumo

Pixel’s announcement explores why Split Fiction uses Unreal Engine 5, focusing on iteration speed and consistent lighting rather than photorealism. It compares the game’s co-op formula with It Takes Two and highlights its split-screen design, changing levels, and release platforms.

DEV Community

Why Split Fiction Bet on Unreal Engine 5: The Boring Co-op Tech Behind a 7-Million-Copy Split-Screen Hit

Split Fiction did the unfashionable thing: it shipped a co-op-only, no-single-player game on rented tech and sold over seven million copies. Developed by Hazelight Studios and published by Electronic Arts, Split Fiction runs on Unreal Engine 5 for PlayStation 5, Windows and Xbox Series X/S (March 6, 2025) and Nintendo Switch 2 (June 5, 2025). It is multiplayer-only, designed for split-screen cooperative play, and follows sci-fi author Mio Hudson and fantasy author Zoe Foster trapped inside their own stories. Hazelight describes it as a sci-fi and fantasy adventure built around hoverboards, gravity bikes, platforming, stealth and puzzles that change every level. That engine choice looks boring until you compare it to Hazelight's own history. It Takes Two was built on Unreal Engine 4, released March 26, 2021 for PS4, PS5, Windows, Xbox One and Xbox Series X/S, and sold over 30 million units by April 2026 after winning Game of the Year at The Game Awards 2021. Same director (Josef Fares), same EA Originals-style publishing, same split-screen co-op-only rule, same trick of giving the two players different abilities every level. Split Fiction is not a new formula. It is the same formula moved from UE4 to UE5. So why rent UE5 instead of building something leaner? The short answer: Hazelight used UE5 for iteration speed and lighting consistency, not for photorealism. What UE5 actually does for this game Unreal Engine 5, developed by Epic Games, was revealed in May 2020 and formally launched April 5, 2022. Its headline systems are Nanite, a virtualized geometry system that auto-manages level of detail, and Lumen, a dynamic global illumination and reflections system. Epic famously used Fortnite as a live testbed, updating it to UE5 in December 2021. Split Fiction does not need Nanite forests or open-world streaming. Its levels are linear, theatrical, and disposable by design: one sci-fi chase, one fantasy dragon ride, then throw the mechanic away. That is exactly where UE5 helps a 60-80 person team: One lighting rig, two genres. Lumen lets a small lighting team keep sci-fi neon and fantasy daylight coherent without baking lightmaps for every one-off set. Mio's cold labs and Zoe's warm forests share the same global illumination logic with different palettes. Redesigned editor tooling. UE5 shipped with new animation and modeling tools in the editor. For a game that invents a new verb every 20 minutes — gravity bikes one chapter, sandsharks the next — in-editor iteration beats raw runtime performance. Current-console baseline. UE4 carried It Takes Two across last-gen (PS4/Xbox One) and current-gen. Split Fiction dropped PS4/Xbox One entirely and targeted PS5, Xbox Series X/S, Windows and later Switch 2. UE5's PS5/Xbox Series optimization, proven on Fortnite, made that cut cleaner than backporting a custom engine. This is not a Nanite showcase like an open-world epic. It is a content-factory use of UE5: spend the engine budget on authoring throughput, not on-screen density. Why not stay on UE4, Godot, or custom tech? Staying on UE4 would have been defensible — It Takes Two already proved 30 million sales on it. Hazelight moved anyway for three practical reasons: Hiring and outsourcing. UE5 C++ and Blueprint talent is easier to hire than UE4-only veterans in 2024-2025, and outsourcing houses had already retooled for Nanite/Lumen pipelines. Switch 2 path. A simultaneous Switch 2 version on June 5, 2025 is easier to negotiate when you are on Epic's actively supported branch with documented scalability settings, rather than a frozen UE4 fork. Sequels cost. Hazelight's design is mechanics-per-level. A custom engine would need to be rewritten every chapter. Renting UE5 turns that rewrite cost into Epic's R&D. Godot or a custom C++ stack would cut royalties but add hiring friction and console-port risk for a studio whose advantage is level design, not engine programming. My take: three contrarian ideas you will not find in the reviews Most co...
Why Split Fiction Chose Unreal Engine 5
Powered by Readybot.io

As últimas novidades de Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …