Unreal Dev Workflow: From Daily Frustration to Daily Momentum | Keegan Gibson | NZGDC 2026

Unreal Dev Workflow: From Daily Frustration to Daily Momentum | Keegan Gibson | NZGDC 2026

Title history
  • Unreal Dev Workflow: From Daily Frustration to Daily Momentum | Keegan Gibson | NZGDC 2026 — observed on 20261110-0839 UTC (YouTube)
🎙 Keegan Gibson (Prismatic Studios) 👥 1K 📅 November 10, 2026 ⏱ 27 min 👁 8 📄 expert opinion 🧭 2026-11-10
Available in: English (current) Français

Keywords

Unreal Game SyncHordeUnreal Build AcceleratorZen ServerRobo Merge

Summary

In this 27-minute conference talk, Keegan Gibson, Head of Engineering at Prismatic Studios, addresses common Unreal Engine development pitfalls such as long build times, mismatched binaries, and editor crashes, arguing that these are workflow problems rather than engine limitations. He introduces five tools built by Epic that sit on Perforce: Unreal Game Sync (UGS), Horde, Unreal Build Accelerator (UBA), Zen Server, and Robo Merge. UGS provides a changelist browser with build status badges and automatically fetches pre-built editor binaries, saving non-programmers from needing Visual Studio. Horde serves as CI/CD and build orchestration, enabling incremental builds and nightly packages. UBA distributes compilation across idle network machines, drastically reducing build times. Zen Server shares derived data, reducing redundant shader cooking and enabling fast asset streaming to devices. Robo Merge automatically merges changes across Perforce streams, keeping branches close and minimizing binary reconciliation pain. Gibson emphasizes that teams should adopt tools based on their most pressing bottleneck, not all at once, and warns that full setup takes about a month of dedicated effort. The talk concludes with Q&A, including practical advice on remote setup and the relative value of each tool.

188 words

Critical Evaluation

Value of the Information & Strength of the Argument

The value of this talk lies in its practical, experience-based guidance. Gibson avoids abstract theory and instead presents tools that have immediate impact on developer morale and iteration speed. He grounds his arguments with relatable examples (e.g., an artist waiting for a build) and concrete numbers (e.g., 45-minute compile reduced to 5-6 minutes with five extra machines). The argumentation is solid: he identifies a clear problem, explains each tool’s role, and provides an adoption order based on pain points. He also acknowledges trade-offs, such as setup time and the necessity of Perforce, which bolsters credibility. The talk is convincing because it prioritizes pragmatism over buzzwords, and the Q&A section addresses real-world concerns like remote work and cloud hosting.

Scientific Rigor, Source Quality, Title Accuracy

The scientific rigor is high from a technical standpoint: the recommendations are consistent with Epic’s official documentation and common industry practices. However, no external sources are cited beyond the tools themselves, and the claims are largely anecdotal, derived from the speaker’s personal experience. That said, the context of a professional conference talk and the detailed, realistic setup expectations lend it reliability. The title accurately reflects the content, focusing on daily frustrations and achieving momentum. No misleading elements were found; the talk is honest about what the tools can and cannot do.

224 words

Title / Content Match

The title accurately reflects the content: the talk addresses daily workflow frustrations and presents a path to momentum through specific tools. No mismatch.

Quality & Reliability

8/10

The talk is based on the speaker's direct experience with real productions, providing practical, actionable advice. While no external citations are given, the content aligns with Epic's official tooling and is presented with realistic setup costs and benefits. The speaker answers questions transparently.

Key Moments

Contribution & Novelties

This talk provides a consolidated, practitioner’s view of Epic’s five workflow tools, explicitly framing them as an integrated system rather than isolated utilities. It offers a clear adoption roadmap based on team pain, honest setup costs, and practical tips (e.g., single Docker command for Horde/UGS/UBA). The contribution is not novel in technology but in synthesis and prioritization, making it useful for studios considering these tools.

Pour aller plus loin :

121 words

Radar Profile

The profile shows strong scores in information quantity and reliability, with slightly lower technical depth. This reflects a talk that is broad and practical, offering a high-level overview of multiple tools rather than deep technical implementation details. The speaker prioritizes actionable advice over exhaustive documentation, which suits a conference audience.

Reliability 8/10