Panel - UE4 Pipelines, Teams and Tools
summary
Panelists compare practical workflows: teams use Unreal Game Sync and Perforce, run CI via TeamCity or Electric Commander, and speed compiles with IncrediBuild (FASTBuild is now viable in 4.21+). Integration takes weeks not days—typically 2–8 weeks per Engine merge—and Fortnite ties updates to a ~10‑week Battle Pass. Shared derived data cache is per‑studio, Builds run every 2–6 hours, precommit checks and an Editor startup time test catch regressions, and hot reload via Live++ dramatically reduces C++ iteration time.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:13Managing engine updates
- 8:26Build infrastructure
- 16:51Handling build failures
- 22:04Version control and locking
- 26:17Build distribution
- 30:19Optimization and editor speed
- 33:55Lessons learned
- 37:31Derived data cache (DDC)
- 41:36Marketplace tools and closing
related talks
54mHow to Apply the Software Engineering Process to the Gamedev Process
54mOptimizing Game Development Workflows with Visual Studio and AI
55mSo You're Trying to Support a Medium Sized Studio....
41mThe Unbreakable Team: Maintaining Build Stability in Unreal Engine
36mImproving Developer Iteration in Unreal Engine 5
32mGame DevOps: Elevating Your Unity and Unreal Build Pipelines With TeamCity
44mHow Sprocket Games Achieved 10x Playtest Velocity for an Unreal Engine Game
43mInside Real-time Production: The Tools that make it Tick