Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.Close
For some reason your suggested change could not be submitted. Please try again in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.Close
Unity offers an Asset Server add-on product for easy integrated versioning of your projects and you can also use Perforce 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 control 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 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
Assets and the
ProjectSettings directories to the system. The
Library directory 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:
Create a new project inside Unity and call it
InitialUnityProject. You can add any initial assets here or add them later on.
Enable Visible Meta files in
Quit Unity (this ensures that all the files are saved).
Library directory inside your project directory.
Import the project directory into Subversion. If you are using the command line client, this is done like this from the directory where your initial project is located:
svn import -m"Initial project import" InitialUnityProject svn://my.svn.server.com/MyUnityProject
If successful, the project should now be imported into subversion and you can delete the
InitialUnityProject directory if you wish.
Check out the project back from subversion
svn co svn://my.svn.server.com/MyUnityProject
And check that the
ProjectSettings directory are versioned.
Open the checked out project with Unity by launching it while holding down the Option or the left Alt key. Opening the project will recreate the
Library directory in step 4 above.
Optional: Set up an ignore filter for the unversioned
svn propedit svn:ignore MyUnityProject/
Subversion will open a text editor. Add the Library directory.
Finally commit the changes. The project should now be set up and ready:
svn ci -m"Finishing project import" MyUnityProject