Why Git users switch to Unity Version Control
Open source, free, and flexible, Git is a popular version control solution (VCS), but it can be daunting for the less technically savvy. When artists run into issues, they need programmers to fix them: It doesn’t integrate with their tools, and buckles under the weight of large binary files common in gamedev.
Unity Version Control won’t break, even with repos in excess of 5 TB, and it handles updates and check-ins faster than other solutions.
Artists can use Unity Version Control independently via Gluon, an easy-to-use workflow with file locking. Coders maintain their standard workflow with full branching and merging.
Choosing a VCS often means deciding whether to work centralized or distributed. Unity Version Control has both: Get the speed and power of Git-style workflows with Perforce-like scalability.
Unity Version Control supports multiple workflows and large files out of the box, so you don’t need to maintain redundant systems or add-ons. Keep your toolchain lean and highly performant.
How does a worker-owned cooperative studio get both artists and engineers aligned on a production process? Read how KO_OP powered collaboration with Plastic SCM (now Unity Version Control).
Read how Sycoforge leveraged Unity tools to manage the growing scope of their project and integrate player feedback for rapid, iterative game development.
Find out why Unknown Worlds chose Unity and Plastic SCM (now Unity Version Control) to help bring Subnautica to life.
Want to get up and running quickly? These instructions can help you set up Unity Version Control for your project in just a few minutes.