Use Plastic SCM version control software to enable teams to collaborate on Unity projetcs.
Learn how to set up Plastic SCM. Leanr how to set up version control in Unity.
Plastic SCM automatically checks files out if you have modified them. The only files that you must specificly check out to modify are Project SettingsA broad collection of settings which allow you to configure how Physics, Audio, Networking, Graphics, Input and many other areas of your project behave. More info
See in Glossary files.
When you edit something locally in your project which has also been edited remotely, a conflict occurs. If your project has conflicts, you must:
If Unity recognises that you need to perform a merge before you submit changes then it prompts you to complete the merge. This takes you to the Plastic SCM client.
If incoming changes conflict with local changes then a question mark icon appears on the conflicting files in the Incoming changes window. Here is a quick guide to resolving conflicts and merging with Plastic SCM:
To lock files with Plastic SCM, perform the following actions:
rep:default lockserver:localhost:8087 *.unity *.unity.meta
In this case all .unity and .unity.meta files are going to be locked for checkout on repository ‘default’.
For more information on locking, see Locking: avoiding merges for unmergeable files and Configuring exclusive checkout (Lock).
PlasticSCM does not support remote activity, like PerforceA version control system for file change management. More info
See in Glossary does. As such, this functionality is unavailable for Plastic SCM in the Editor. Statuses such as: “Checked out Remote” or “Out of Sync” aren’t displayed in the Project windowA window that shows the contents of your
Assets folder (Project tab) More info
See in Glossary.
Learn more about distributed version control.
Learn more about distributed and centralized version control.