Scaling Indie - Making Bigger Games With Unity
summary
Unity projects scale into real problems: asset storage grows to 32 GB of source assets, builds swamp editors and take days to sync, and nested prefab references bloat memory. The pipeline uses SVN, Jenkins build machines that auto-upload to Steam/TestFlight and graph uncompressed textures, Trello for task/bug tracking, and heavy reliance on the Asset Store plus plugins like Marmicet Skyhop, InControl and Amplify Color. Kickstarter and Steam Early Access deliver actionable QA; localization hits ~55,000 words and costs weeks and thousands of dollars.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 5:58Source control challenges
- 11:01Unity Asset Store tips
- 16:00Build automation
- 21:46QA from Kickstarter
- 27:44Optimizing draw calls
- 31:37Iteration at scale
- 32:29Q&A
related talks
46mUnity Tech for Indies
01h 16mindie design
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
55mSo You're Trying to Support a Medium Sized Studio....
41mPanel: What Tools all Game Developers Should Have at Hand at all Times
45mTop 10 Unity Assets That Every Project Should Use
51mEmpowering Design: The Tools and Pipelines of Unpacking
38mGrowing a Healthy UE4 Ecosystem