Bringing Destiny to Stadia: A postmortem
summary
Bungie ports Destiny 2 to Stadia in about six months by adding a Vulkan Linux build, targeting 60 FPS and cutting encoder latency through immediate present mode, plus direct peering from Destiny servers into Google data centers to reduce network lag. Pipeline creation averages ~12 ms so a bespoke pipeline pre-create system plus offline cache and automation reduce hitching across hundreds of bubbles, thousands of gear items and seasonal updates; small dedicated team plus Google support hits certification targets and resolves motion‑sickness and perf issues.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:53What We're Talking About
- 2:37Exciting Technology
- 3:32Partner with Google
- 4:12Destiny History
- 4:42Stadia Tech Stack
- 9:45The Team
- 10:15How was 6 months possible?
- 11:39Instances
- 12:11Engineering Workflow
- 12:24Deployment
- 12:52Package Flow
- 13:48Switching Builds
- 14:05Easy Playtests
- 14:32Scaling Up
- 15:05Developing on Stadia
- 16:12Early Investigations
- 16:48Simulated Average Case
- 17:19Simulated Worst Case
- 17:49Focus on Low Latency
- 20:14Optimization Pass
- 20:51Playtest Time!
- 21:34Refresh Rate Issue
- 22:36Present Margin - Old
- 23:19Present Margin - Immediate Mode
- 24:09Final Playtest
- 24:30Game Feel - What else was done?
- 25:09What is Vulkan again?
- 25:28Pipelines and Pipeline Cache
- 27:17Building Your Pipeline Cache File
- 29:01Automation
- 29:33Another Solution Needed
- 31:52Pipeline Cache Plan
- 33:17Reporting
- 34:03Wrap-Up
related talks
40mStadia Streaming Tech: A Deep Dive
09mTop 10 Stadia announcements
50mUnity GDC Showcase 2021
39mWhat's New in Gaming at
59mThe path to leveraging DOTS in production
52mOptimising your game AFTER it ships
16mHigh-density Mobile Cloud Gaming on Edge SoC Clusters
51mCloud Native Development Level Up for Smaller Teams