Source Control & Remote Team Collaboration
summary
Recommends Perforce (also Plastic SCM, Git, SVN) and shows concrete setups: file locking, Swarm code reviews, shelving, and Perforce streams to avoid duplicating engine builds. Shares tuned server settings (disable net autotune, enable parallel transfers) and a cheap home-built topology: 60 TB storage, 1 TB Gen4 M.2 RAID giving ~27 GB/s write, 9–10 Gbps network, 256 GB RAM, total cost under $10k. Uses Typemap rules, VLANs, offsite/on-site backups and a UGS layer; claims engine build times drop from days to about four hours.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:51Overview
- 2:52Perforce - Pros & Cons
- 5:40Plastic SCM - Pros & Cons
- 6:52Additional Resources
- 7:46Source Control UI
- 11:48User Workflow (typical)
- 13:47Code Review/Staging
- 14:49Modifying Revision Workflow (typical)
- 19:56Considerations
- 27:20Perforce Server Replication
- 36:53Perforce Streams
- 45:07Nested Subscenes (Sequencer)
- 45:50Parent Materials
related talks
54mHow to Apply the Software Engineering Process to the Gamedev Process
33mVersion control for game developers
30mA Deep Dive into a Cross-Platform Build Farm
20mDevelopment efficiency with expert CI/CD strategies
44mPanel - UE4 Pipelines, Teams and Tools
55mSo You're Trying to Support a Medium Sized Studio....
28mPushing Git repos over the speed limit.
46mThe Software Factory