Growing a Healthy UE4 Ecosystem
summary
Company standardizes C++ and Blueprint rules by shipping them as coding standards as source code checked in and evolved via code reviews, and enforces naming and content rules with Editor commandlets plus CI validation that elevates cook warnings as errors. Build orchestration uses Epic BuildGraph with TeamCity/Jenkins, distributed compilers (Incredibuild or Fastbuild) and AMD Threadripper machines to get a full rebuild in under 15 minutes on UE4 4.21; pre-commit personal builds use cached incremental objects to cut validation to ~15 minutes. A custom test-only module API lets unit and functional tests touch private runtime state; merge workflow usually completes in about two weeks but can break content (one 4.21 merge turned meshes into single triangles).
AI-written summary · about
chapters (8)
- 0:00Start
- 3:35Game Module Layout Example
- 6:57The standard
- 19:07BuildGraph (example)
- 20:29Normal Commit Flow
- 20:43Pre-Commit Flow
- 26:51Unit Test Example
- 33:04Architecture
related talks
55mSo You're Trying to Support a Medium Sized Studio....
54mOptimizing Game Development Workflows with Visual Studio and AI
54mHow to Apply the Software Engineering Process to the Gamedev Process
36mImproving Developer Iteration in Unreal Engine 5
28mTaking the Heroic Leap from a Proprietary Engine to UE5
30mA Deep Dive into a Cross-Platform Build Farm
44mHow Sprocket Games Achieved 10x Playtest Velocity for an Unreal Engine Game
46mUnity Tech for Indies