Plastic SCM is Trash - riddled with Issues

I logged into unity and Plastic SCM was not logged in, so the button stated "Collab"

I clicked the cloud button to login and collab pops up stating I cannot sync because project is Plastic SCM.

I restart Unity and Plastic SCM button now appearing properly.

However, now I have 623 conflicts dating back to 90 days of all my own work showing in Plastic SCM. ( I have been using plastic for 90 days with hundreds of commits.)

I can resolve some of them, but many are directory conflicts from deleting or renaming a file.
These need to be resolved first, yet there is no way to resolve them. Clicking, right clicking, or selecting the item does not enable any context menu to resolve them whatsoever. The resolve button is disabled when these items are selected in the conflicts list window.

So since I cannot resolve my dir conflicts, I cannot move on to resolve all the other conflicts listed, which are about 590 conflicts!

I do not advise anyone to use plastic SCM, it has been unreliable and a conflict generating system for the 3 months that our project has been "upgraded" to plastic.

This has basically upgraded Collab into an unreliable VCS and conflict generating system.
This is the 3rd time we have had to lose all history due to Plastic SCM.

I would like my stable COLLAB system back, how do we go back to regular Collab? if possible please advise.
If Collab is no longer available, I still wish to have this Plastic SCM completely removed and to not have access to my projects in any form whatsoever. I literally do not ever want to see Plastic SCM ever again.

[Edit]
By the way, the project does not even show up in my cloud account on Plastic SCM website. So I Cannot wipe the project and restart my version history.

 

I am on Unity 2019.4.34f1.
Version Control Package is 1.14.27

I went through each conflict that was unresolvable, and kept my changes in the Plastic client, and Unity editor plastic SCM is now cleared up, so I cant share any screenshots any more.

This was definitely Plastic SCM connecting and thinking all of the last 123 commits over 90 days were not mine, even though I was listed as the owner. It was literally trying to compare my project files (current) with every single commit I pushed in last 90 days.

As I stated above, this was because Plastic was not logged on, and when trying to logon (cloud icon) it tried to start collab. I have since removed Collab setting it to "Off" in my services.

Also, FYI:

I installed the client to fix conflicts ( successfully) and it installed some things for VSS.
When building, I now get these warning errors when building:

2>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "log4netPlastic". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
2>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Unity.Plastic.Antlr3.Runtime". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
2>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Unity.Plastic.Newtonsoft.Json". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
2>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "unityplastic". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

So I uninstalled the Cloud client, and the warnings are still there.

Now how do I get rid of these warnings?

 

I uninstalled version control completely. Because it was crashing. Plastic SCM kept popping up anytime I made a change in the inspector. I am still getting these errors when building, and I have version control package UNINSTALLED.

3>------ Build started: Project: Assembly-CSharp-Editor, Configuration: Debug Any CPU ------
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "log4netPlastic". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Unity.Plastic.Antlr3.Runtime". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Unity.Plastic.Newtonsoft.Json". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "unityplastic". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Unity.PlasticSCM.Editor". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3> Assembly-CSharp-Editor -> C:\Users\Andy Llora\Documents\Unity 2019.4.12f1\QuadriemMobile\Temp\bin\Debug\Assembly-CSharp-Editor.dll
========== Build: 3 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

I need to completely remove anything related to Plastic from my project, this is simply unacceptable to have version control crashing my project and prohibiting builds.

How do I remove all references to Plastic in my Visual Studio 2017?

 

Nothing in plugins folder related to plastic.

 

Hi guys,
You made backups a nightmare with plastic SCM, most of us are alone developers or very small teams, we don't want features that need hours or days of learning for this simple and crucial backup task.
In addition plastic SCM is always closing the connection after a while.
I suspect Plastic SCM to close connection of free accounts when they exceed a certain amount of file transfer to save bandwich.
For me it was a total waste of time (I tried 3 times that killed 3 days) and it ruins my Unity user experience.
I bought a 2T hard drive to make my own backups to solve the problem once for all.
I am sure you can do better guys.

 

Assembly 'Packages/com.unity.collab-proxy/Lib/Editor/PlasticSCM/unityplastic.dll' will not be loaded due to errors:
unityplastic references strong named Newtonsoft.Json Assembly references: 12.0.0.0 Found in project: 13.0.0.0.
Assembly Version Validation can be disabled in Player Settings "Assembly Version Validation"

Code (CSharp):

1. Assembly 'Packages/com.unity.collab-proxy/Lib/Editor/PlasticSCM/unityplastic.dll' will not be loaded due to errors:
2. unityplastic references strong named Newtonsoft.Json Assembly references: 12.0.0.0 Found in project: 13.0.0.0.
3. Assembly Version Validation can be disabled in Player Settings "Assembly Version Validation"

This is an absurd situation:

• I'm not using your version control
• it is referencing an old outdated version of Newtonsoft.Json
• producing two 'errors' every time I compile to test (not critical errors at least, but they still annoy me)
• I already removed it from my project (see point 1)
  
• it started when I installed a pack of VFX - what has VFX got to do with version control?

Very annoying, I was on a roll until this interrupted my flow.

 

@carlosalba1985 Thank you for the reply.
I'm using Unity 2021.3.10f1 for this project.

While typing this I went to grab a screenshot of the package manager but I found 'version control' is listed again (and yes it's 1.5.7 - an outdated version). Two days ago I cleaned this project of all the cruft and the plastic version control was definitely part of that. I also see Timeline, ProBuilder, Polybrush, and Test Framework are there... they were all part of that clean-up too.

Is it possible that some other package that I've installed brought these packages back in? I regularly see messages saying that a package has package manager dependencies, and always permit them. If that is a possibility, how do I stop it from happening regularly?

As a side-note, the reason why I've started paying attention to all these packages is that Unity takes too long to get started (on my powerful PC with ultra-fast SSD drives). If I have a 60 minute coding window, I don't want to spend 3-5 minutes waiting for the tool to do something obscure before I can start. I was hoping that by getting rid of this stuff I might have a more responsive editor. Plastic SCM was my first target because several times I've seen the loading dialog mention it despite me not using it for anything. The others got caught up in that cleaning spree.