Best Version Control for Unity

Yes, I know there is no the best tool, etc. All I want is your advice. Here are my situation and questions:

• I want to choose between Git and Perforce.
• I heard that Perforce is an industry standard but some people on forums say they hate it. Why is that so?
• I heard that Perforce is much harder to work with when it comes to branches. Is it that horrible?
• Some people say that Git is not ready for studios despite some of its pros. Is that right as for now?
• Has something changed as for now with these two tools?

All info I found was from 2 or more years ago so I want to check if something has changed since then.

 

Hi, did you find the answer? Can you share your thoughts? We are also looking for the best solution with unity. Thanks

 

Git. I use this professionally within my company, and I use it personally. It's good for business, it's good for opensource. Merging is a breeze, and getting help is easy. It is very rare to bump into someone using Perforce. I recommend starting with a client like git-fork. I haven't used Perforce myself but I see no reason to use anything other than Git, it's perfect.

 

The problem with unity and source control is that you want to store not only source but also all those GB of assets.

We used Git in our 5 years project. We had to partition it into multiple git projects in order to push it all onto the server.

 

This is why git-lfs was made. LFS stands for Large File Storage. It puts all your binaries on a separate FTP server and only diffs the links in the git history. LFS is a MUST when using git with unity.
There are plenty of different ways to install LFS depending on your git client, but here's a cli tutorial:
https://github.com/git-lfs/git-lfs/wiki/Tutorial

 

You talking about remote storage though right? I made a git repository for my game that's over 2GB right now and tried to push it to bitbucket but failed because there limit is 1GB. I think if your keeping your repository local you can just use git.

 

LFS pushes to a separate FTP server which is usually at Bitbucket or Github. They both have limits on how much space you have on your free account. There is probably a way to setup git to use your own FTP server, but i haven't looked into it.

 

I've used perforce and i've used GIT, both are based on UNIX, those die hard people that love to type on a command line because they consider that work! as of 8/6/2020 there is no graphical interface that will actually work great, the unix peeps still have an edge on the whole VCS apps, Microsoft Team Server is the best if you want graphical interfaces, Perforce is practically useless in unity as too is GIT, it don't work and will NEVER do what you want, it's confusing and pointless, NONE of the tutorials will help, it's designed for die hard hackers and unix coders that love to type 200 character line items. i suggest just make backup file and ignore VCS until source control comes out of the 70's

 

I recommend Plastic SCM.

As @drslaphead pointed out, Git is very developer oriented. When I tried Git+Git-LFS late 2018, I had to install multiple softwares, activate it through command prompts and had no ideas what was my current storage print, the pricing, the limitations or even if it was configured properly. I can't work with that.

The problem with git in my experience is that it's a tool designed by developers, for developers, and while it's great if you're working 100% on code and fluent with everything code based, it won't do the job for a Unity project because it needs to be usable by everybody.

That's where Plastic is different. It is designed for projects containing all kinds of assets like textures or 3Dmodels while still retaining branching and merging on files that will allow it.

 

How about Unity Collaborate?

 

Please define a smaller team?

 

I'd define smaller teams as 1-10 people. Usually an indie studio, or just a rando group working on a game.
When you start to get more corporate with it, you see company scale implementations of software packages like Atlassian, AWS, etc. For example, my company uses Atlassian products for issue tracking, version control and documentation, while using the Microsoft products such as Teams, Sharepoint, and Azure for more administration based things.

Small teams CAN work on big games though, so I'd say if your game is getting beyond 10GB, you probs want to look into something other than git. Im doing research into Plastic now because im running our project in 3 different git repo's simultaneously to cope with reserialisation issues

 

We started using Perforce. Then moved to Visual Studio Team Foundation Server. We had problems with both at times where Perforce or TFS thinks you have the latest version of a file when you really didn't and had to force download that file.

We are now using Git and LFS. It's working for our multiple teams but it has the largest learning curve.