Unity offers an Asset ServerLegacy - An asset and version control system with a graphical user interface integrated into Unity. Enables team members to work together on a project on different computers. More info
See in Glossary add-on product for easy integrated versioning of your projects and you can also use PerforceA version control system for file change management. More info
See in Glossary and PlasticSCM as external tools (see Version Control Integration for further details). If you for some reason are not able use these systems, it is possible to store your project in any other version controlA system for managing file changes. You can use Unity in conjunction with most common version control tools, including Perforce, Git, Mercurial and PlasticSCM. More info
See in Glossary system, such as Subversion or Bazaar. This requires some initial manual setup of your project.
Before checking your project in, you have to tell Unity to modify the project structure slightly to make it compatible with storing assets in an external version control system. This is done by selecting Edit->Project Settings->Editor in the application menu and enabling External Version Control support by selecting Visible Meta Files in the dropdown for Version Control. This will show a text file for every asset in the
Assets directory containing the necessary bookkeeping information required by Unity. The files will have a
.meta file extension with the first part being the full file name of the asset it is associated with. Moving and renaming assets within Unity should also update the relevant
.meta files. However, if you move or rename assets from an external tool, make sure to syncronize the relevant
.meta files as well.
When checking the project into a version control system, you should add the
Packages and the
ProjectSettings directories to the system. The
UserSettings directories should be completely ignored - when using .meta files, it’s only a local cache of imported assets.
When creating new assets, make sure both the asset itself and the associated
.meta file is added to version control.
First, let’s assume that we have a subversion repository at
svn://my.svn.server.com/ and want to create a project at
Then follow these steps to create the initial import in the system:
InitialUnityProject. You can add any initial assets here or add them later on.
UserSettingsdirectories inside your project directory.
svn import -m"Initial project import" InitialUnityProject svn://my.svn.server.com/MyUnityProjectIf successful, the project should now be imported into subversion and you can delete the
InitialUnityProjectdirectory if you wish.
svn co svn://my.svn.server.com/MyUnityProjectand check that the
ProjectSettingsdirectory are versioned.
UserSettingsdirectories in step 4 above.
svn propedit svn:ignore MyUnityProject/Subversion will open a text editor. Add the Library and UserSettings directories.
svn ci -m"Finishing project import" MyUnityProject