Ethan Clarke
Unity Plastic SCM is a version control system optimized for game development and 3D projects. It allows for better collaboration between artists and programmers by providing separate GUIs to facilitate two different workflows within the same repository. To set up Plastic SCM Unity, you need to first download Unity Version Control from the Plastic SCM website and follow the installation wizard. Once installed, you will be prompted to launch your preferred workflow type and sign in or sign up for an account. After that, you will need to create a workspace for your project and connect it to your Plastic SCM Cloud repository. With your workspace set up, you can now use the Plastic SCM window to manage your file changes and start creating!
| Characteristics | Values |
|---|---|
| How to get started with Unity Plastic SCM | Download Unity Version Control from the Plastic SCM website and follow the installation wizard |
| Choosing a workflow | Select the type of workspace you prefer: Plastic (for programmers) or Gluon (for artists) |
| Signing in | Sign in or sign up for an account using your Unity ID or a Plastic SCM account |
| Creating an organisation | Create a new organisation or select an existing one |
| Creating a workspace | Create a new workspace for your project in the Plastic SCM window or in the Plastic SCM GUI |
| Viewing and managing file changes | Use the Plastic SCM window to view and manage file changes, including new and changed files in your project |
| Comparing file versions | Right-click on a file in the Plastic SCM window and select "Diff" to compare the updated file with the previous version |
| Reverting changes | Select the file in the Pending changes tab and select "Undo changes" to revert to the previous version |
| Locking files | Create a lock.conf file in your server directory and specify the repository and server |
| Viewing locked files | Open the terminal/command line window to view a list of locked files |
| Testing locked files | Check out the same file with a different user to see an error message in Unity's console |
| Viewing project history | Go to the Changesets tab to view the project history of changes made to the repository and who made them |
Explore related products
What You'll Learn
Download Unity Version Control and follow the installation wizard
To set up Plastic SCM Unity, you need to first download Unity Version Control. You can do this by visiting the Plastic SCM website and downloading the installation wizard. Once you have downloaded the wizard, follow the on-screen instructions to install Unity Version Control.
After the installation is complete, you will be prompted to launch your preferred workflow. Unity Version Control provides two separate GUIs to facilitate collaboration between artists and programmers. The Plastic GUI is designed for programmers, while the Gluon interface is tailored for artists. You can switch between these two interfaces at any time using the top-right menu in the client.
Next, you will be asked to sign in or create an account. It is recommended to use a Unity ID, even if you do not plan to use Unity as your game engine. Once you have signed in, you will be directed to the Plastic home screen. If you do not have any organizations associated with your account, you will need to create a new one.
With your account set up, you can now select your preferred type of workspace. Unity Version Control supports separate workspaces within the same repository, allowing for optimized game development and 3D projects. The Plastic workspace is designed for programmers and is distributed, while the Gluon workspace is centralized and intended for artists.
Now that you have selected your workspace, Unity Version Control will display your project files in the "Pending changes" tab. You can choose specific files to include or add all files to the repository by selecting them and clicking "Check-in changes". The system will automatically perform a check-in for relevant folders and files, such as package files and project settings. Once this initial asset check-in is complete, you are all set up and ready to start creating with Unity Version Control.
Molds for Crawfish Soft Plastics: DIY or Buy?
You may want to see also
Explore related products
Choose your preferred workflow and workspace
After installing Unity Version Control, you will be prompted to select your preferred workflow. Unity Version Control offers two different workflows within the same repository to facilitate collaboration between artists and programmers. The Plastic workflow, designed for programmers, is distributed, while the Gluon workflow, designed for artists, is centralized. This choice is not permanent, and you can switch between the two interfaces in the top-right menu of the client.
Once you have chosen your workflow, you will be asked to create a workspace for your project. A workspace interacts with version control, allowing you to download files and make necessary changes for each check-in. You can have multiple workspaces connected to the same local repository. Plastic SCM automatically creates an ignore file in your project folder to exclude certain files from version control. This ensures that files that should not be part of the repository are not tracked.
The Plastic workspace is ideal for branching, merging, and pushing/pulling changes. It provides greater flexibility and control over your project files. On the other hand, the Gluon workspace is suitable if you primarily need to check in your work and synchronize it with your teammates' changes.
After setting up your workspace, Unity Version Control will display your project files in the Pending Changes tab. You can choose specific files to include or add all files to the repository. Version Control will automatically perform a check-in for appropriate folders and files, such as package files and project settings. Once your initial asset check-in is complete, you are ready to start creating with Unity Version Control.
How Plastic on Windows Solves Condensation Problems
You may want to see also
Explore related products
Set up your account and organisation
To set up your account and organisation, you will first need to download Unity Version Control from the Plastic SCM website. Follow the installation wizard instructions, and you will then be prompted to choose your preferred workflow type. Unity Version Control offers two distinct interfaces: Plastic, designed for programmers, and Gluon, tailored for artists. This choice is not permanent, and you can switch between the two interfaces as needed.
After selecting your preferred workflow, you will be directed to sign in or create an account. It is recommended to use a Unity ID even if you are not employing Unity as your game engine. If you do not have any organisations associated with your account, you will need to create one.
Next, you will choose your preferred workspace. The Plastic workspace is distributed and optimised for programmers, while the Gluon workspace is centralised and intended for artists. Once you have made your selection, Unity Version Control will display your project files in the Pending Changes tab. Here, you can select specific files to include or add all files to the repository by checking the relevant boxes.
After completing the initial asset check-in, you will be all set up with Version Control for Unity and ready to start creating.
Merging in Plastic SCM: A Step-by-Step Guide
You may want to see also
Explore related products
Manage your file changes and view project history
Unity Version Control is a version control system optimized for game development and 3D projects. It supports separate workflows within the same repository. The Plastic workspace is designed for programmers, while the Gluon workspace is for artists.
To manage your file changes, you can use the Plastic SCM window in the Unity Editor. This window displays a list of new and changed files in your project. When you add a new file or save changes to an existing file, the affected files are automatically displayed. To open this window, select Window > Plastic SCM.
The Pending Changes tab in the Plastic SCM window shows your existing project files as "Added" and "Private". To include these files in your workspace, you must check them in. Once checked in, the Pending Changes tab will no longer list these files. You can choose specific files to include or add all files to the repository by selecting them and clicking "Check-in Changes".
To view the history of changes made to your project, use the Changesets tab. This tab displays all changes made to your project chronologically, along with who made the changes and when. Double-clicking on a file in a changeset will show the File History tab, displaying every changeset for that file. You can also view the history of each file by right-clicking and selecting "View File History".
The Magic of Plastic Transformation: From Raw to Product
You may want to see also
Explore related products
![[100 Count] Clear Plastic Forks Heavy Duty, Premium Disposable Forks, Durable Plastic Cutlery for Parties, Picnics, Big Event, Daily Use - Heat Resistant & BPA Free](https://m.media-amazon.com/images/I/71BiJVdS6-L._AC_UL320_.jpg)
Lock files and resolve merge conflicts
When using Unity to develop games, merge conflicts can occur when multiple people are working on the same project. Resolving these conflicts is simple in the Unity Editor. To do so, navigate to the Incoming Changes tab, which lists all the incoming changes from the Plastic SCM repository. When there is a file conflict, the list will be highlighted. To resolve this, select the conflicting file(s) and right-click on them to select how you would like to merge them.
You can also resolve merge conflicts in the Version Control window. Click on the 'Apply all incoming changes' button, which will take you to the Plastic SCM GUI client. Within the client window, click 'Explain merge' for a visual understanding of the changes. Now click 'Process all merges' and another window will display. Here, you will be shown the individual conflicts and given the option to choose what changes to keep or discard. Once you have solved the conflicts, click on 'Save and exit', and the merge operation will be completed.
To prevent merge conflicts, it is advisable to update your workspace frequently. This reduces the chances of a merge conflict as you would be making changes to the most recent repository changeset. If multiple people are working on the same project, it is also recommended to avoid working on the same files.
To lock files using Plastic SCM, you must first create a lock.conf file and place it within your server directory. You can find your server directory from "..\PlasticSCM\server". In your lock.conf file, specify the repository you are working on and the server that will complete the lock.
Sunlight's Effect: Plastic Degradation Speed
You may want to see also
Frequently asked questions
First, download Unity Version Control from the Plastic SCM website and follow the installation wizard. You will then be prompted to launch your preferred workflow type. You can choose the Plastic workspace for programmers or the Gluon interface for artists. Next, sign in or sign up for an account and create or select an organization.
You can manage your file changes in the Plastic SCM window. To open this window, select Window > Plastic SCM. The Plastic SCM window will display a list of new and changed files in your project.
To compare an updated file with the previous version, right-click on the file in the Plastic SCM window and select Diff. This will open the Differences view, which will allow you to compare the repository source with your local copy.
