Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Some questions after updating from integrated Plastic support to Package Manager

Discussion in 'Unity Version Control' started by GlowfishInteractive, Dec 5, 2021.

  1. GlowfishInteractive

    GlowfishInteractive

    Joined:
    Mar 7, 2016
    Posts:
    5
    I'm currently updating our project from Unity LTS 2019.4.17f1 to 2019.4.33f1.

    Since the build in support has been removed and we are forced to switch to the Package Manager Version Control package solution.
    We've been using Plastic for the past couple of years and it's really cool to see that improved integration is coming but as it stands this update process hasn't been super smooth, starting out with our project settings asset causing errors spams as the old integration was removed without a clean catch for projects that update from an existing setup.

    Once I got everything working I did notice that you need to have the Plastic SCM window open at all times for the checkout, editor change icons and source control features and options to be functional.
    I couldn't find anything in the documentation referring to this. (
    Is this by design? Will this be changed in the future so you don't need this window running constantly?

    Additionally (and rather annoyingly) it seems like I'm now forced to enable the unity services/ set up a cloud project ID?
    At least it seems that a cloudProjectId is generated and assigned in the ProjectSettings.
    (Not sure is this is related to the package or just Unity in general. But as I'm not using any of the services or plan to use any of the services. This seems like Unity is trying to force people into another subscription package.)
    Is there any way to work around this or disable this? I just want to use my existing source control setup and account without being forced into an additional service setup that I don't really care for and is completely unrelated to Version Control.
     
    Last edited: Dec 5, 2021
  2. Sravzz

    Sravzz

    Unity Technologies

    Joined:
    May 13, 2020
    Posts:
    29
    Thanks for bringing this up to us. I am checking with the team regarding any planned future changes for the window needs to be opened. Will get back shortly.
     
  3. marie-unity

    marie-unity

    Unity Technologies

    Joined:
    Aug 6, 2019
    Posts:
    67
    This is not the intended behavior, you should be able to view Plastic SCM toolbar notifications, icons, contextual buttons and contextual menus when the window is closed. The contextual menu and notifications are available, but it seems like the contextual buttons and the icons in the project view are not. This has been flagged and we will look into this.
     
  4. GlowfishInteractive

    GlowfishInteractive

    Joined:
    Mar 7, 2016
    Posts:
    5
    The Enable Forced Checkout of unity assets option is also not working when the window is closed down.
     
  5. marie-unity

    marie-unity

    Unity Technologies

    Joined:
    Aug 6, 2019
    Posts:
    67
    This has been flagged as well. Thanks for reporting this @GlowfishInteractive .
     
  6. GlowfishInteractive

    GlowfishInteractive

    Joined:
    Mar 7, 2016
    Posts:
    5
    We're encountering some additional issues as well.
    Whenever we want to check out an asset from within prefab mode we get the following message: "Version Control : Cannot check out files in offline mode" - We then need to navigate to the project window, find the prefab and check it out from there before opening it to check it out.
    This used to work fine with the old build in integration so I'm guessing something isn't working correctly here as well. (This also slows down work quite a bit)