I’m not sure how I got in this state, but whenever I create a new project (I’m using Unity 2021.3.10f1, but this also happens with other versions) I get thousands of ‘PlasticSCM’ missing reference errors, like this:
Library\PackageCache\com.unity.collab-proxy@1.17.2\Editor\PlasticSCM\AssetMenu\AssetFilesFilterPatternsMenuBuilder.cs(1,14): error CS0234: The type or namespace name 'Client' does not exist in the namespace 'Codice' (are you missing an assembly reference?)
I have to remove the ‘Version Control’ package from the package manager to fix it. I don’t use, nor have I ever used, Plastic SCM and I’m not sure what library ‘Codice’ is in or why I don’t have it.
Installing or reinstalling new or old Unity versions doesn’t fix it.
Anyone have any ideas what might be causing this? Thanks
Yep. Unity.
I really hate when people reflexively blame Unity.
But in this case, they are the culprit. You certainly didn’t ask to install it!!
Extra unwanted packages in new projects (collab, testing, rider and other junk):
https://discussions.unity.com/t/846703/2
About the fastest way I have found to make a project and avoid all this noise is to create the project, then as soon as you see the files appear, FORCE-STOP (hard-kill) Unity (with the Activity Manager or Task Manager), then go hand-edit the Packages/manifest.json file as outlined in the above post, then reopen Unity.
Sometimes the package system gets borked from all this unnecessary churn and requires the package cache to be cleared:
https://stackoverflow.com/questions/53145919/unity3d-package-cache-errors/69779122
2 Likes
Thanks, but yeah, I couldn’t be bothered to track down the real issue.
So I uninstalled unity hub and all unity installations, deleted all unity and unity hub AppData, and all left over unity dll’s in program files, etc. Reinstalled and works again.
I think this problem originated from an aborted project upgrade in Unity hub, which then caused the ‘Failed to connect to package server’ issue you can find lots of threads about.
1 Like