Unity Community


Results 1 to 4 of 4
  1. 3.5 beta and External version control

    Hey Everyone,

    I am working with the unity 3.5 beta and am trying to set my project up for external version controls to use with tortoisesvn. I am looking at this article here and it all seems really straight forward except for the library files it seems that the contests of this folder have changed in 3.5 and some of these .asset files are not present.

    Does any one know which files need to be saved and which ones can be deleted for the 3.5 beta version?

    thanks.


  2. Location
    Leeds, UK
    Posts
    2,060
    In 3.5, all files in /ProjectSettings need to by synced.

    The /Library files had to be half-synced and half-not so it's been split apart so that everything that needs synced resides by themselves in one folder (i.e. /ProjectSettings).

    That documentation's for the last official release (and so outdated for 3.5) - I think the 3.5 beta changelogs detail what needs syncing, perhaps the local documentation in your Unity install does too, I've not looked at it yet :P
    Last edited by Farfarer; 02-08-2012 at 01:37 PM.


  3. Location
    New Jersey
    Posts
    791
    I highly suggest using the beat documentation (should have been installed locally along with 3.5 - my instal is here: file:///C:/Program%20Files%20%28x86%29/Unity/Editor/Data/Documentation/Documentation.html)

    Here is the 3.5 version of that page:
    Using External Version Control Systems with Unity

    Unity offers an Asset Server add-on product for easy integrated versioning of your projects. If you for some reason are not able use the Unity Asset Server, it is possible to store your project in any other version control system, such as Subversion, Perforce or Bazaar. This requires some initial manual setup of your project. In addition, moving and renaming of assets needs to be performed using your version control client and not inside Unity.
    External Version Control is available in all versions of Unity.
    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 clicking the Enable button. This will create 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. When moving or renaming assets in the version control system, make sure you also move or rename the .meta file accordingly.
    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 external version control, 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.
    Example: Creating a new project and importing it to a Subversion repository.

    First, let's assume that we have a subversion repository at svn://my.svn.server.com/ and want to create a project at svn://my.svn.server.com/MyUnityProject. Then follow these steps to create the initial import in the system:

    1. Create a new project inside Unity and lets call it InitialUnityProject. You can add any initial assets here or add them later on.
    2. Enable Meta files in Edit->Project Settings->Editor
    3. Quit Unity (We do this to assure that all the files are saved).
    4. Delete the Library directory inside your project directory.
    5. 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.
    6. Check out the project back from subversion
      svn co svn://my.svn.server.com/MyUnityProject
      And check that the Assets and ProjectSettings directory are versioned.
    7. 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.
    8. Optional: Set up an ignore filter for the unversioned Library directory:
      svn propedit svn:ignore MyUnityProject/
      Subversion will open a text editor. Add the Library directory.
    9. Finally commit the changes. The project should now be set up and ready:
      svn ci -m"Finishing project import" MyUnityProject

    Here's the TL;DR for 3.5 EVC


    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 external version control, it's only a local cache of imported assets.

  4. Awesome, thanks guys.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •