The path to leveraging DOTS in production
summary
Two teams report concrete DOTS outcomes: a 15‑person VR MMO uses hybrid ECS (GameObject+Entities) to tag actions, queue saves to avoid external storage rate limits, and keep client/server logic in one project; a racing title builds mostly in DOTS, uses sub‑scene streaming and Burst/Jobs for animation and car handling, and ships a state‑record‑and‑replay QA tool that reproduces bugs, speeds iteration and resumes races after OS kills. Reported wins include ~3 ms GPU savings on low‑end devices and up to 12–15 ms in hotspots; costs are learning curve, API churn and occasional platform FP discrepancies.
AI-written summary · about
chapters (11)
- 0:00DOTS and ECS introduction
- 7:57Zenith’s hybrid ECS architecture
- 9:24Detonation Racing’s ECS streaming
- 11:08Zenith’s multiplayer challenges
- 13:39Detonation Racing’s ECS determinism
- 23:34Balancing GameObjects and ECS
- 28:12Experimental ECS challenges
- 34:02DOTS roadmap for production
- 36:32Entities 0.50 features
- 38:45Entities 1.0 goals
- 44:55Q&A
related talks
59mWhy DOTS Is Unity's Silver Bullet
43mIntroduction to Data-Oriented Design in Unity
08mCodemotion Berlin 2019 I Ciro Continisio, Lead Evangelist, EMEA - Unity Technologies (Interview)
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
50mUnity GDC Showcase 2021
08h 28mJetBrains GameDev Days 2024
50mDomain-driven Game Design
52mOptimising your game AFTER it ships