From Liquid to Unreal: Why We Ditched Our In-House Engine
summary
11 bit studios runs a six-month feasibility study that compares business and schedule risk of keeping the custom Liquid Engine versus technical and management risk of moving to Unreal, builds a tech demo and a Unity prototype, then decides to switch. The team reorganizes into four domains, runs a two-week Unreal warmup and a game‑jam, scales to Scrum Nexus with 70+ people, shifts QA to QA builds designer tools, and iterates team roles.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:54What's the idea behind this presentation?
- 3:4911 bit studios technical development timeline
- 5:21Liquid Engine 1
- 5:57Road to Liquid Engine 2
- 9:28Feasibility study
- 9:56Initial approach
- 12:36Feasibility process focus change
- 15:38Risk analysis - Liquid Engine vs Unreal Engine
- 17:10Recommendation for Unreal Engine
- 19:58Overview
- 23:17Transition process
- 27:19Technical structure after transition
- 27:45Technical structure now
- 30:36Unreal Engine project organization in Agile/Scrum
- 33:58Real-life development structure
- 35:59QA changes
- 39:49Conclusions
related talks
19mTechnical indie game developer tips for starting your framework early
54mHow to Apply the Software Engineering Process to the Gamedev Process
38mGrowing a Healthy UE4 Ecosystem
37mDash Bash
46mWorkflow on Fortnite
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
59mThe Decisions it Takes to Run a Successful Game Studio
34mArchitecting Content for a Live Service Game