Documentation Guides
Guide

Version control

What to use instead of (or alongside) GitHub when the project gets heavy: by team size and engine.

Why plain Git isn't enough

Git is built for text. A game is mostly binaries: maps, .uasset, textures, audio. Those files can't be merged: if two people edit the same map, one loses their work. That's why file locking matters in games (whoever opens it locks it), and why the system must handle files of hundreds of MB.

What to use by team size

TeamUseWhy
1 to 5 people Git + LFS with file locking, or Diversion Free or cheap, and locking keeps people from overwriting binaries.
5 to 15 people, lots of artists Perforce Handles huge files well and locking is part of the workflow.
Large team on Unreal Perforce + Unreal Game Sync Artists get precompiled builds and never touch C++.
Team on Unity Unity Version Control, Git + LFS or Perforce Unity Version Control is built into the editor.

The options

Git + LFSGitHub, GitLab or Bitbucket with Git LFS for large files. Turn on locking (git lfs lock) for maps, .uasset, .psd and other binaries: almost nobody uses it and it solves much of the problem.
Perforce (P4)The standard at large studios. You lock a file while you work on it and nobody else can submit it. It has a free plan for small teams (check the current limit on their site); the real cost is usually the server.
Unreal Game SyncIt isn't another version control system: it's an Epic tool on top of Perforce that distributes precompiled builds so artists open the editor without compiling. It's recommended with a source build of Unreal inside the project (200+ GB): only worth it on large projects.
DiversionCloud version control built for games and large files, with no server to set up.
Unity Version ControlFormerly Plastic SCM. Built into Unity, also works with Unreal and supports file locking.
SVN / AssemblaAssembla hosts SVN, Git or Perforce if you don't want to run the server.

Fork, GitHub Desktop or Anchorpoint are visual clients: they make Git easier to use, but don't solve large binaries on their own.

Rules that save you trouble

  • Lock binaries: maps, .uasset, .psd, .blend, audio. With Git LFS mark them as "lockable".
  • Don't commit what gets generated. In Unreal: Binaries, Intermediate, Saved and DerivedDataCache. In Unity: Library, Temp, Obj and Logs.
  • One map, one person at a time. If several people work on the same level, split it into sublevels or use One File Per Actor in Unreal.
  • Back up off the server: the repo isn't a backup if it lives on a single machine.

In StudioOps

StudioOps doesn't replace your version control. When you edit a project in My Studio you pick which system it uses and paste the repo or depot URL; it shows up in the project's links. In Assets and Pipeline, "I'm working on it" tells the team who has each asset, before it ever reaches the repo lock.