how to work with a team of 3+ people?

Unity Engine
1

well…i just bought the unity iphone, and we have it in more than one computer (3 or more people working on the same project). Reading in the forums, i saw that svn is not compatible because the way of metadata is stored.

I have no money for buying the assets server, and we need to update our work.

The question is… what can i do to solve this problem?

P.S: i’m new to the mac world, so if your answer could be detailed i would really appreciate it.

thanks a lot.

2

as the meta data etc are all stored binary, the asset server is the only way without having to fully upload / download after each change.
no concurrent work on the project would be possible

3

thank you.
Which folders/files would i have to upload/download if i want to work with another app? and which (free or low-cost) app would you recommend me for doing it?

Thanks a lot.

4

Hi Blackwind,

Like Dreamora said, it’d be pretty much the whole project after every update. Normally I’d recommend subversion or git, but Unity’s binary format for metadata precludes any sort of merging - you’d get conflicts all the time if more than one person is working on it.

If you want to go that route, it’d be better to export and pass around Unity packages than to attempt some sort of shared folder schema.

5

If you’re uploading downloading from a server, working, then uploading to that same server, I’d use Fetch. It’s like $20, and it works great.

Just a note, this system is not ideal for your use because, like said, the metadata wouldn’t merge well, if at all. If you can figure out how to merge Unity metadata, tell us.

6

so the “solution” is to make sure that nobody works on the same file at a time right?

i saw that Fetch is an ftp client… it looks nice.
And which subversion type app is nice for mac?

thanks a lot.

7

In the same Object, to be specific, whatever it is (be it a scene, a prefab, a material, or anything else).

I’ve said before, most of the advantages of version control systems are lost, since you won’t be able to merge between branches or multiple changes. If you’re using them, you’ll have to limited them to your source. Otherwise you’ll get no end of unsolvable conflicts on the binary data.

If you still wish to use one, and you haven’t used version control before, start looking at tutorials for subversion and git. After I started using git I’m not likely going back to svn, but subversion has friendlier UIs available.

For Git, a good starting point is: https://peepcode.com/products/git

For subversion, look at svnx. Be aware that’s only the UI, you’ll need to set up the server as well.

8

I’ve been using Dropbox (www.getdropbox.com) to sync between multiple computers I use without issue.

9

Thanks for mentioning them, Jeff. I’d heard of them back when they were in closed beta, and promptly forgot about them - they seem like a very good choice for someone without experience in vcs.

10

Note that you can version-control script files with subversion and the likes. Off the top of my head those are the only assets which do not come with unity meta-data (which, as said, is where the trouble of non-asset-server version-control begins).