Comments on: Using SVN and UAS to Synchronize Library Code in Unity

By: 女子徵信

女子徵信 — Fri, 30 Sep 2011 02:08:25 +0000

This is my first time i visit here! I found so many useful stuff in your website especially its discussion. From the a lot of comments on your articles, I guess Im not the only one receiving the many satisfaction right here! keep up a good job;

By: Adam

Adam — Wed, 16 Feb 2011 15:35:46 +0000

Hi Eric,

I wasn’t suggesting that UAS versions the “Library folder instead of the Assets folder.” Using UAS or external version control will both version files in the Assets folder. The difference is that when you use UAS, much of the metadata for assets (e.g., import settings) is stored in files in the Library folder, and UAS can hook into these files directly through the Unity editor. External version control, on the other hand, requires that such metadata be exposed in sidecar data files (.meta) that will live in the Assets folder, and which you must manually check in/out and move along with your assets.

As for your other question, yes, you still have to commit the changed files to each UAS-managed project when you push them out using SVN. Adding the SVN layer on top is basically intended to be a way to maintain common code across several projects. The reason I do this is because I otherwise prefer UAS for versioning assets (e.g., it does not require creating all of the .meta files, it does not require that all project participants have Maya installed in order to import native Maya files, etc.).

By: Eric

Eric — Wed, 16 Feb 2011 15:13:06 +0000

Hey Adam. First, love your blog and your Unity products (I purchased biped editor, and will probably get the Handles library). I only started using Unity last month, and I’m weighing the pluses/minuses of the Asset server. You say that it operates on the Library folder instead of the Assets folder and that it doesn’t require synchronization of out-of-band data files. By these I assume you mean things like .psd or .ma files that you might not keep in the asset folder. But surely it must sync items in the asset folder itself? And why would it sync the Library folder since it is derived from the asset folder? I’m clearly missing something here. Also, I understand your need to sync library code across multiple projects, and I watched your video. But again, being very new to all this, I got a little lost when you say “push” the changes to other projects. UAS is going to just see these as local changes in the other projects, so won’t you have to commit these with UAS as well? Sorry to be so dense; I’m just used to the ways of other game engines (i.e. severe pain).

By: Daniel Brauer

Daniel Brauer — Mon, 10 Jan 2011 20:36:40 +0000

We don’t use sparse working copies, but if I’m reading the last paragraph on this page right, that’s not currently possible:

http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html

It doesn’t seem to have changed in 1.6, either, so the only solution I can think of is to carefully check out a new sparse copy and omit the file. Kinda stupid.

By: Adam

Adam — Mon, 10 Jan 2011 17:42:10 +0000

Out of curiosity, do you guys use the sparse checkout features much? I’m totally new to Cornerstone, but I’ve found one problem I have yet to solve. For example, if I accidentally add a file or folder from my library to a sparse working copy, or if something changes in my library such that some dependencies are no longer necessary in a sparse working copy, I can’t figure out how to remove them from the working copy. Obviously I can’t delete it and check that change in, and I can’t add it to the snvignore settings either. Any tips?