Improving Data Structures for Rapid & Intelligent Gameplay Design.
summary
A modular propulsion and drivetrain system replaces monolithic vehicle classes so components are assembled by data not hard code, stored as structs with unique IDs in a central database; the editor adds one-click swapping of component sets and simultaneous editing that propagates changes to every referencing vehicle. Static analysis and real‑time telemetry drive automated tests and quick tuning. A legacy car could have ~1400 parameters now normalized into reusable parts, drastically lowering the learning curve and speeding iteration.
AI-written summary · about
chapters (16)
- 0:00Ubisoft and vehicle simulation
- 2:37Talk structure and vehicles
- 5:26Challenges with old system
- 9:57Vehicle editor limitations
- 11:00Technical debt inefficiencies
- 15:15Missing features and future
- 16:17Restructuring propulsion
- 20:30Modular vehicle design
- 24:44Data storage reorganization
- 27:10Benefits of new system
- 29:37Designer tools improvements
- 34:14Database growth and reuse
- 35:35Tool and database updates
- 37:46Static analysis and testing
- 40:14Summary
- 41:18Q&A
related talks
25mDeveloping Games Using Data not Trees
43mIntroduction to Data-Oriented Design in Unity
35mHow to Create Scripting Tools That Designers Love
01h 05mData Storage in Entity Component Systems
08mCreative Console: A Player-driven Game Based on A Modular Fast-Evolving-And-Verifying Framework
29mPlatform Engineering Principles in Complex Systems
46mTechniques for making reusable code
41mBuilding Tools Quickly: Blueprints, Menus, Utilities, and Widgets