Search Unity

Unity's version control component has been upgraded to Plastic SCM.

Plastic SCM on Linux

Discussion in 'Unity Collaborate' started by jvetulani, Feb 17, 2022.

  1. jvetulani

    jvetulani

    Joined:
    Dec 20, 2016
    Posts:
    55
    After this absolutely unacceptable automatic migration in the middle of a work week...
    the new Plastic SCM doesn't work for people using Linux in the team with an error:

    Could not find a part of the path "/home/myUser/Projects/Unity/NameOfMyProject/Packages/com.unity.render-pipelines.universal@10.7.0/-Textures/Packages/com.unity.collab-proxy/Editor/PlasticSCM/Assets/-Images/d_iconundo.png".
     
    jvetulani, Feb 17, 2022
    #1

  2. jvetulani

    jvetulani

    Joined:
    Dec 20, 2016
    Posts:
    55
    Weirdly the path changes each time you spam click Reload in the Plastic SCM window.
     
    jvetulani, Feb 17, 2022
    #2

  3. jvetulani

    jvetulani

    Joined:
    Dec 20, 2016
    Posts:
    55
    The issue was resolved (so far) by changing to the latest version of the Version Control package and the addition of "com.unity.nuget.newtonsoft-json": "2.0.0" to manifest.json - it was previously installed by collab as a dependency, but some packages rely on it.

    Installation of the standalone Plastic SCM app was troublesome, since they have undocumented dependencies, the unity button "Launch in Plastic SCM" asks us to install Plastic SCM, proceeds to download and then does nothing. The Branches button in Unity also does nothing.
     
    jvetulani, Feb 17, 2022
    #3