Unity Version Control

Does anyone have any suggestions for Version Control with Unity? I'm manually backing up my files right now and it's maddening. I'm just using Unity's personal edition right now because I'm not a production company

 

Git

 

I use and like Subversion. (I also use and dislike git.)

Basically, use whatever you prefer. See this page of the manual.

 

I also highly recommend using version control. Git, SVN, whatever is better than just manual backups. You're probably going to find a lot more information about Git these days; for example, what hosting providers support SVN? I don't even know. With Git you can use GitHub for open-source projects, but BitBucket or GitLab give you free private repositories.

 

Searching for "SVN hosting" turned up the following results on the first page of Google.

http://www.cloudforge.com/
https://riouxsvn.com/
https://sliksvn.com/
https://projectlocker.com/

Some hosting providers support repositories for no additional charge with their basic plans.

https://www.dreamhost.com/hosting/shared/

Cloud servers have become very inexpensive and setting up a custom repository can be done in minutes.

https://www.digitalocean.com/products/droplets/

 

bitbucket hosts private projects for free. I believe with Unity personal edition you can use Unity Collaborate but I ran out of free space pretty fast so I pay $9/month for Unity Team Advanced, which includes Unity Cloud Build (which pulls out of Collaborate)

 

Awesome thanks! Seeing as I have only a few months of coding experience, do you have any recommendations on how to learn to use Git?

I've done some UI design for developers and they use Git too, but I have no idea how to get started on it, how it works, or what standard protocols are for it

 

This tutorial is a decent place to start.

 

According to this docs page, "Unity supports version control integration with Perforce and Plastic SCM."

I haven't used either of these before. Does anyone have experience with these, who can comment on advantages? Does the support that Unity provides for them give any benefits when compared to using an external VCS?

E.g. how do they compare to Git or other free alternatives when used in conjunction with Unity.

 

I tried Perforce because of that page. I wasn't a fan. The "Unity supports" stuff just means there is some integration into the editor. It is kinda nice for example that I can send my updates to the Perforce server from within Unity. Editor integration isn't actually of much importance though, and trying to teach remote developers how to properly use Perforce inside and outside of Unity was more trouble than it was worth.

I much prefer just using standard tools outside of the editor with SVN.

 

Thanks for sharing your experience.

It does seem like most developers prefer to use an "external" VCS.

 

Windows can back up your files for you, automatically: https://support.microsoft.com/en-us/help/17143/windows-10-back-up-your-files

Also, the "previous versions" feature of Windows can be life saving: https://www.tenforums.com/tutorials...rsions-files-folders-drives-windows-10-a.html

I'm also sure there exist back up software out there that can do that easily for free.

If you use git, you'll have to update your projects on their site manually anyway... I also gave up using git after I experienced some problems with it and I had to reinstall Windows.

 

Personally, I think Unity Teams is worth the $9 a month. It makes things easy with how well integrated it is.
If you wanna try it out first there is a free option, though it offers significantly less space.

 

I had a project I needed to create a repository for anyway, so I decided to record the process today. Right away this will give you the ability to look at past commits on Github.com, in case you changed something and want to see how it previously was.

This is just a minimum to get started. You should also study what version control is and how Git works in depth. To learn Git properly, check out these pages by Git Tower:

https://www.git-tower.com/learn/git/ebook/en/command-line/introduction

I don't use Git in a professional capacity, so please be aware I might make mistakes and probably use terminology wrong.

https://git-scm.com/downloads
https://github.com/