Find out all you need to know about the move to Plastic SCM, Unity's version control system (VCS) built for game development
Watch the Unity Plastic SCM team offer hands-on support to help navigate the upgrade and answer questions. View Recording.
Through optimized workflows for artists and programmers and superior speed with large files and binaries, Unity Plastic SCM is a version control and source code management tool built to improve team collaboration and scalability with any engine.
Starting on December 1, 2021, we will begin automatically migrating projects from Collaborate to Plastic SCM. Once this is complete, your Collaborate projects will be archived and available to Export only.
While the Collaborate projects themselves have been archived, they are still available to Export. You have until February 28, 2022 to export your data from archived Collaborate projects from this location Unity Dashboard > DevOps > Collaborate > Storage on the Unity Dashboard. On this date, all archived projects will be deleted permanently.
You will also need to update settings for any Unity Cloud Build projects that are using Collaborate for source control management, or have Integrations that rely on Collaborate. You can get more information on how to update your Cloud build setting here.
The Plastic SCM package allows for in-editor version control and it's functionality will be more similar to Unity Collaborate. The Plastic SCM package is supported in the below Unity versions:
Other Unity versions will need to use the Plastic SCM Cloud Edition client, which can be downloaded here.
If you are on a supported version of Plastic SCM for Unity, after opening your project in the Unity Hub, you will see a pop up prompting you to upgrade your Collaborate project to Plastic SCM. Completing this step will convert your local workspace to a Plastic SCM format automatically.
If you are on one of the supported versions of Plastic SCM for Unity, use the Unity Hub to access your project.
For supported Unity versions (see above), the Collaborate icon will be replaced by a Plastic SCM icon in the Unity Editor.
Use the Pending Changes tab to complete what is known as the Publish action in Collaborate. In Plastic SCM, this is called Checkin Changes.
Check the Changesets tab to view your project history. Any changes previously done in Collaborate will still be available via Plastic SCM. You can go back to previous revisions, even if they were done using Collaborate prior to the Plastic SCM upgrade.
The Plastic SCM icon turns yellow when new changes are available for your project.
The Pending Changes tab is where you will checkin changes you've made to the project to send to your repository.
The Changesets tab will show you the project history of changes made to the repository and who made each change. Clicking on each changeset listed will allow you to see which files were impacted by that changeset.
You can also view the history of each file by right-clicking and selecting "View file history" which will show you a list of changes made to the file. You have the option to right-click on an earlier version and select "Revert file to this revision."
Whether you are using Unreal Engine, a version of Unity that doesn't support Plastic SCM for Unity, or another engine, you can still use Plastic SCM's full functionality by downloading the full client.
Download and install Plastic SCM Cloud Edition.
Open the Plastic SCM client and log in using your Unity ID.
Select your Plastic SCM cloud organization to start working on it.
Choose between Gluon mode (a workflow tailored for artists) or the Developer mode.
If your Unity project files are already on your machine, select the path on disk that corresponds to the root of your Unity project. If not, select any location in which you want to create your workspace.
If you choose Gluon, configure your workspace to load the Unity project files you want to work with.
If you choose Plastic, update your workspace to ensure your project is up to date with all the incoming changes.
If you are using Unity, open your Unity project through the Hub.
Use Plastic or Gluon, to check in your changes (for example, adding a scene) after saving them to the project in your editor. This is the way to send the changes to the repository. Every time you check in, a changeset is created.
The changesets show you the project history of changes. If you double-click a changeset, you'll see which files were impacted by that changeset.
You can also view the history of each file by right-clicking it and selecting "View file history". You have the option to right-click on an earlier version and revert to this revision.
Unity is committed to crafting DevOps and version control solutions for an inclusive collaborative environment that accommodates all team members, regardless of their role and technical expertise.
To get a better idea of what's been released, what's in progress, and what's on the horizon, take a look at our product roadmap page.