ryancassell

Awesome, I'm glad we're on the same page! Have you tried removing the Newtonsoft Json package from your Unity Project in the Package Manager to see if you still get any errors? You should be able to continue using the Version Control package using the dll supplied by the Twitch library package. I didn't encounter any errors in the Console or drop in functionality with the Version Control package when testing on my machine after removing Unity's Newtonsoft package.

Hi Pascal, Adding the Newtonsoft.Json.dll to my project finally reproduces the issue for me, thank you for bearing with me. So just to confirm, the DLL you provided was from the Twitchlib package you want to use. That DLL is a newer version of Newtonsoft, compared to the 2.0.0 version of the package in Unity, which is the one that the Version Control package depends on. And there's no way that Twitchlib can be used with just the Unity-provided Newtonsoft package, correct? That is why you'd like the Newtonsoft package that is currently used by the Version Control package to be updated to the more recent version. Do I understand the situation properly now?

Thank you for supplying your manifest and package. I used the manifest to make a new 2020LTS project and added the Newtonsoft package you provided to that project, but I still don't get any conflicts between it and the Version Control package. I do see the Dependencies field for the Version Control package like what you shared previously, so I can confirm that it's using it (along with Services Core). Could you also try sharing with me the Twitchlib package? Maybe there's another conflict in there that's the culprit of the errors?

Thank you for the added screenshots! I tried to reproduce the issue on my end (by adding the Newtonsoft Json 2.0.0 package with Version Control 1.13.5) but didn't experience any conflict errors. I've reached out to the dev team for more help. I noticed in your Package Manager that you're able to see that Newtonsoft Json is depended on by Version Control, but I don't see that kind of dependency on my machines with the Newtonsoft package. Please share with me the manifest.json of your project (located in your project's Packages folder) as well as the manifest.json for 2020.3.22f1 in the following directory: For Windows: C:\Program Files\Unity\Hub\Editor\<your-version>\Editor\Data\Resources\PackageManager\Editor\manifest.json For Mac: Applications/Unity/Hub/Editor/<your-version>/, Show Package Contents, Contents/Resources/PackageManager/Editor/manifest.json

Hi @Pascal, The Version Control package has a Newtonsoft.dll that has been renamed to Unity.Plastic.Newtonsoft.Json.dll to avoid naming conflicts like this. Could you share screenshots of the errors you're seeing that show there's a conflict with the Netwonsoft.dll so that we can use them to further diagnose the issue? Could you also tell me if there's a specific Unity package or asset that is using v13.0.0 of the dll that is conflicting with the Version Control package?

I understand the confusion. You actually don't need to change the Version Control mode to Plastic SCM in the Project Settings menu to use Plastic SCM. That Version Control mode is related to the Legacy Integration for Plastic SCM that is no longer supported. We will be removing that option from the dropdown once the new Plastic SCM package exits beta. This would help explain the unexpected layout changes that you're experiencing. I apologize for the confusion with these settings. It sounds like changing the Version Control Mode creates compiler errors in the Version Control package. When that happens, then both the Inspector checkin/checkout options and the Windows menu option fail to load. If you leave the Version Control Mode setting alone, then that should resolve your issues.

Hi @TimoB, it is by design that Unity switches the Version Control Mode to Visible Meta Files when Plastic SCM (and other VCS) systems are enabled. This makes it easier for those systems to track the .meta files, which are vital for syncing the status of Unity assets across projects. As for breaking your Layout settings, I'm sorry to hear that. Could you attach screenshots that show what your original layout was like and what is changing when Plastic SCM is enabled?

Apologies for the late response. I was out for jury duty. Thank you for the additional info. In the future, I would not recommend downgrading a Unity Editor to a previous major version, especially from 2020 to 2019. The Package Manager does not handle this edge case very well and can result in trying to load packages that are not supported on older versions of the Editor. Like you found out, the Version Control package implements the UI differently for 2019 vs 2020+ versions of the Editor, which creates a lot of Version Control-related compiler errors when you downgrade a 2020 version of the project to 2019. Since you mentioned that you removed the Version Control package and was suddenly able to see the Plastic SCM context menu again, by any chance are you using the Plastic SCM for Unity Plugin from the Asset Store? (You can confirm this by checking if your project has a Plugins/PlasticSCM folder.) I ask because the context menu should only be visible if you either have the asset store plugin (which has been deprecated because it currently conflicts with the Version Control package) or the Version Control package of at least 1.7.x. If the above is the case, then you should be able to return to Unity 2020.3, delete the PlasticSCM folder in the Plugins folder, then install the latest recommended Version Control package from the Package Manager to resume working as expected (with context menu intact).

Hi @Hydrasin, I'm sorry that Plastic SCM is missing in the context menu of the Project Browser for you. That's very odd that it seems to only come back when the .plastic folder is removed from your project. Could you tell me the following so that we can try to reproduce it? Unity Version OS Version Control package version

Hi @kieryst, I'm sorry to hear that this is happening to your project. Could you tell me the following so that we can try to reproduce it on our end? Unity Version Version Control package version When you notice that references are missing in a prefab, does it happen in all of your prefabs or just some of them? Also, were there any recent checkins that included changes for those prefabs before you noticed the missing references?

Hi Alan, I'm sorry you're encountering this issue. This sounds like an issue we discovered recently where typing "Shift + O" in the comment field is unintentionally interpreted by Unity as a request to open an asset in the Project Browser. We've pushed a fix to v1.12.6/1.13.6 of the Version Control package, but I can't give a specific ETA of when this version of the package will be available just yet. Regards, Ryan

Hi Alan, those errors you're seeing related to the Plugins folder sound like you may be using the deprecated version of the Plastic SCM Unity Plugin. The version on the Asset Store is no longer being updated now that it has been merged into the Version Control package, which you can download from the Package Manager window in the Unity Editor. I strongly recommend that you delete the Plastic SCM folder in your Plugins folder (since it will create compiler errors if both versions are installed in the same project), then install the Version Control package from the Package Manager. Do NOT delete your .plastic folder in your project's root folder so that the Version Control package can read from that folder to put you back in the same state you left off in without having to make any other changes. Let us know if you run into any issues with the transition process.