Great Unity, thanks for this - I just lost connection to project in the Plastic SCM - how I am supposed to work right now?
I have restarted Unity.
I have removed and installed Version Control package - no resolution.
Error in project settings, “connect” does not work:
Package is installed:
No Plastic SCM menu:
Hi @sergiusz308 , I’m sorry that you’re running into this issue. It appears that you’re trying to use the Legacy Plastic SCM Unity Integration via the Version Control mode in the Project Settings. This integration is no longer supported since it’s being replaced with the more robust and integrated Version Control package.
To resume working with Plastic SCM in your project, please do the following:
The Version Control package will detect your existing .plastic folder for your project and allow you to resume working in the workspace after you’ve logged into your existing Plastic SCM account, either via email or Unity SSO.
FYI: You may need to close and reopen the Plastic SCM window from the Window menu after logging into Plastic SCM if the window asks you to create a workspace. Currently, the plugin does not always smoothly handle the flow of reconnecting to an existing Plastic workspace after logging in for the first time. But reopening the Plastic SCM window should resolve any issues you run into during this process.
Please let me know if you have any more questions or concerns.
@Ryan-Unity Thanks for responding, but your resolution is completely useless, because:
Screenshot from the OP:
When I switch to “Visbile Meta Files” I have Asset Management menu grayed-out:
So there’s no way I can return to Plastic SCM window or inspector.
So I hope that this time you guys would read carefully statement of the problem and I can’t wait to hear about next steps, because so far, upgrading to 2021.2 is a disaster.
Apologies for the misunderstanding, I appreciate your patience.
On top of the Plastic SCM window menu option, there are a couple other ways to open the Plastic SCM window:
As for why the Plastic SCM menu option is missing in the Window menu, that is unusual. Could you send me a copy of your project’s manifest.json in your Packages folder so that I can see if the team can reproduce the issue on their end?
@Ryan-Unity No problem, thanks for following this up.
So, good news is that I managed to bring Plastic SCM inspector following your tip on context menu - it worked:
As you can see however I still don’t have that little Plastic SCM button visible, nor anything else related to version control.
When I make changes to assets changes appear in the “Pending Changes” tab and it all work (checking-in / out). I got icon overlay working on the changed assets as well:
Bad news is that “Version Control” menu is still grayed out and there’s no Plastic SCM menu is missing (I restarted unity several times, no effect):
PFA manifest file you requested (“manifest.rar”). There’s also “packages-lock.json” file in the same folder - I don’t know if this is of any importance.
Also I don’t know if this is a thing but I don’t see “version control” packager in the manifest file, however I do have “Version Control” marked as “installed” in the Package Manager:
7617181–946879–manifest.rar (566 Bytes)
I’m happy to hear that you were able to open the Plastic SCM window using the context menu in the Project Browser, and that it’s finding your changes. I’m also happy to see the rest of the feature working by
I saw in your screenshot that you looked for the Plastic SCM button in the top right of your Editor window. My initial screenshot might not have made this clear, but in 2021.2, the Plastic SCM button (along with the Account and Cloud buttons) were moved to the top left of the Editor window. Can you include a screenshot of that part of your window to see if the buttons are missing there, please?
I’d like to clarify that the Version Control menu in the Asset Management section of the Window menu is not related to the Plastic SCM window. That menu option, which is related to the legacy integration for Plastic, Perforce, and other VCS, is supposed to be grayed out when a Plastic workspace has been detected in the project and the Version Control package is installed, so it’s working as expected. What isn’t working as expected is that the Plastic SCM window menu is missing, like you mentioned and showed in your screenshot.
One quick aside regarding the name of the Version Control package: the Version Control package is listed as the com.unity.collab-proxy package in the manifest. This is so that the Version Control package can allow users to smoothly transition from Unity Collaborate to Plastic SCM by including the source for both. I hope that clears up any confusion about why you aren’t seeing a Version Control-specific package in your manifest.
Thank you so much for including your manifest! I dropped it into a new 3D project on my Windows machine running Unity 2021.2.0f1, but there were no compiler errors or warnings that got in the way of the Plastic SCM Window menu option or Editor button from appearing in the Window menu on my end. Would you mind sharing any other errors you see in your Console?
@Ryan-Unity Thanks for detailed explanation. I don’t know guys who has this idea to move important icons, such is version-control to the opposite side of the screen and not mention about that in the release notes.
I guess you guys hire some professionals to run product management, right? I understand that Unity is a complex software but men, this are kind of a important things to just skip them like that!
Yes, I have these icons on the left side:
I appreciate your time and effort to explain this! I hope that people responsible for keeping documentation up to date would do their job next time better, so you would not have to wade chin up in the frustration of the peoples just loosing their grip because frigging version contorl button (and the whole inspector!) just decided to play hide-n-seek.
p.s. I didn’t experience any errors in the console.
Happy to help. I’ll definitely pass this feedback along to our UX designers and docs team so that they can take it into consideration. I was also surprised by the new UX, so I understand how you feel but I’m sorry that it led to so much frustration.
I’m glad that you’re able to use the Plastic SCM window and continue working on your project. Please let us know if you run into any more issues.
@Ryan-Unity I had the same issue, I just upgraded to 2021.2.0f1, removed the legacy package, installed the version control package and there was no Plastic SCM option in the Window menu. I made some of the same mistakes as Sergius (like changing the version control option in the Project settings). But thankfully I found this thread. Got the window open using the context menu. Then noticed the buttons on the left (which didn’t show the Plastic button anyway). Turns out the Plastic SCM button and option in the Window Menu don’t show up at all until you login into your Unity account and my Unity Hub had logged me out without me noticing it (probably after updating it). They really should mention this in the documentation. It only said you had to setup your Plastic SCM account and I was expecting to use the Plastic SCM window from the Window menu to do it… But I guess the confusion is because my project was already using Plastic before hand? Docs only show setting up for the first time/checkout.
Hi @Alverik , thank you for bringing up the frustration you experienced too. I’ll pass this feedback along to our Docs team so that we can update them to be clearer. Upcoming versions of the Version Control package should be usable without needing to be signed into Unity, at the very least allow you to open the Plastic SCM window so that you can being logging into Plastic SCM.
Hey all, I have students attempting to upgrade projects to Plastic SCM. They all have their organizations setup individually, have been working on Collab just fine. We’ve updated to Unity Hub 3.0.1, Version Control Package 1.15.12 and are using Unity 2020.3.14f LTS. Half of the students are getting the migrate option when opening a project and are able to more forward just fine. The other half are getting Collab errors the first time they log on for the day, then on a reboot of the project, Collab works but no migrate comes up. The Window->Plastic SCM is greyed out for these students, so they can’t open the window there either and I’m not seeing any obvious log errors. The icon they have is the old Collab one, as it is still seen as a Collab project. Any ideas on what might be going on? This is a lab, so all the computers are set up the same way.
Hi @JimVerhaeghe , I’m sorry that half of your students are having issues migrating their projects from Collab to Plastic. It’s possible that this inconsistent experience is due to the Editor version being used by your students being slightly behind the minimum supported Editor versions. Because the Plastic SCM component requires some specific Editor-side changes in order to work correctly, the Version Control package is only supported on the following minimum versions of the Editor:
Could you have your students who are having issues migrating their projects upgrade their Editor version to 2020.3.15f1, then re-open their projects to see if the migrate dialog pops up as expected? If that doesn’t work, then I’d recommend that they re-download their project via the Hub. After the migration, all future downloads of a former Collab project will instead download the Plastic SCM workspace so that they can start working right away.
I hope that this helps to unblock your students and please let me know if they run into any more issues.
Thanks for the information. It takes time to upgrade to a different version for a district this large but I will try. They have yet to convert the project, so not sure if removing it and re-downloading it will work. Will try that today and let you know.
Ok, finally got a version that is Plastic SCM ready installed on my lab computers and am testing the conversion process. For some students (on the old version 2020.3.14f1) the migrate button happened automatically so I expected the same here with the new version we are using (2020.3.30f1). Unfortunately that did not happen with my test account (I can’t use mine as it is already converted to Plastic SCM). When I open a project, it still shows the collaborate symbol at the top right (next to the cloud services icon). If I attempt the drop down window where Plastic SCM should be - it is greyed out.
I just loaded the project, so it had not been opened with a collaborate version before on this machine (we are at the most updated Version Control package (1.15.13). Not sure what to do, as the Unity walk-through show us linking the account (or organization) to Plastic SCM using the Plastic SCM integration - yet we can’t open it.
Any help would be appreciated. It is much easier to teach when students are all on the same setup.
→ Unfortunately this step did not work either.
I am going to have students try the Migration Wizard, as they are all owners of their own organizations. Perhaps this will work.
With your test account and new project, you mentioned that you hadn’t enabled Collaborate yet, is that correct? If that’s the case, then you should have seen in the Windows menu both the Collaborate and Plastic SCM options to allow you to select one of them to open their respective windows. Is that not the case?
Can you double check in the Project Settings if Collaborate is somehow enabled in your new project? Collaborate will need to be disabled first if you want to switch over to Plastic SCM manually. The Migration dialog only pops up for local instances of projects that were migrated from Collab to Plastic SCM on the backend already. An email is sent to the Unity Org Owner once this process is complete for all Collab projects in their Org.
If you created a new test account to test the migration, then you would need to use the Collab Migration Wizard (and then wait 10 minutes), then re-open the Collab Project before the Migration dialog can appear, asking to convert the local Collab Project to a Plastic Workspace. Does that help to clarify things? I’m still confident that this upgrade of Unity Editors should make the migration easier for your students that still haven’t migrated successfully yet.
No, I had a project on collaborate that I downloaded into the new version and updated it on load. The Plastic SCM option is greyed out and not selectable. When I had this happen before, I did not do anything on the back end, a migrate option just appeared (and my students definitely would not know how to do that). It is really odd that it happens sometimes.
I think I figured out how to turn off Collaborate (using the Cloud Services tab, choosing Collaborate then turn it off). Then the Plastic SCM is no longer greyed out and I can have students associate their account with Plastic SCM that way. Assuming that works, then they will get the migrate option locally.
Since we are migrating local copies, is this why the package manager gets updated each time the migration happens? Even if there are no changes (files are identical) Plastic SCM wants to check the files in. Would this issue be fixed by migrating by organization first, rather than each local copy as they open them (though I am assuming migrating local copies has to happen anyway)?
Gotcha, since your test project was still a Collaborate project and wasn’t migrated on the backend, the Migration dialog won’t pop up for it. What you just did is exactly the process I was going to suggest you do to manually switch from Collab to Plastic.
As for the Package Manager updates you’re seeing after you migrate, which files are you referring to? Is it your manifest.json in the Packages folder, or other Project Settings that you are seeing updated?
I believe it is both the manifest.json and one other. I will look into it when i convert one of my other projects at home.
I find it odd that some of my students got a pop up to migrate (as did I) without going online to do the back end migration. Is it possible that their default organization (the one associated with their username) was upgraded without their knowledge?
I did get one of the students to test migrating their organization, and it worked fine (even on 2020.3.14f1). Though there are issues with it still showing the collaborate icon even though the project has been converted. Part of that may be due to school firewall issues.
Thanks for your help.
