How do you collaborate with Pro?

Unity Engine
1

I have never been able to use , let alone try, and of the ‘free’ ways of collaborating with Unity, and me and a group have some money to spend (can easily afford pro monthly payment). I have been trying to look around, and everything about collaboration I have been finding as been dubbed “without pro”, and never provides any answers I am looking for. I thought at first the cloud build would help, but after a 20 minute video , i was wrong.

2

The same way you collaborate with Unity Personal Edition, some form of version control on a server. Most I’ve seen use git hosted either on GitHub, BitBucket, or a private server.

1 Like
3

As DanielQuick said, you don’t need Pro to collaborate anymore, you can use git, Mercurial, the 20 free user license of Perforce, SVN, and others. Any major source control will work with Unity Personal Edition. There are plenty of tutorials and hosting services that can get you setup quickly (see this thread). You can also use the asset/cache server, although I don’t have any experience with it, and most people use one of the above options.

Cloud build is for making builds more for continous integration, deployment and testing (so you don’t need a developer to sit and wait on a build, you can just check your code in, it runs and gives you the results).

There are some basic things you can do to make a project ready for source control and collaboration:

  • In the Unity Editor, go to the menu bar and navigate to Edit → Project Settings → Edtior.

  • In the inspector, look for the Version Control dropdown, and select one of the following options:

  • General source control - Visible Meta Files. This works with Git, Mercurial, and SVN.

  • If you’re using the Asset Server, select that option instead, you can log into the Asset Server with this enabled.

  • If you’re using Perforce, select that option instead. You can log into a Perforce Server with this enabled.

  • If you’re using PlasticSCM, select that option insead. You can log into a PlasticSCM server with this enabled.

  • In the same Editor Settings inspector, look for the Asset Serialization dropdown, and change it to Force Text. This makes it easier to look at the changes to assets and have source control handle merging better.

2 Likes
4

I switch out the settings, as said. and nothing uploads except the ‘.gitattributes’ and ‘.gitignore’(Unity version).

5

Have you marked the project files for adding?

I recommend using SourceTree as a git gui client, so you can see what files are untracked (under assets) and are available to add.
Your .gitignore should be setup to ignore the Library and Temp directories, never commit them (it’s effectively Unity’s Local cache when source control is enabled). I’ve had to fix repos that had those directories checked in before.