Jump to content

Plastic SCM in Linux editor issues/Assets folder getting set to private


JVetulani

Recommended Posts

Unity Version: 2020.3.22f1
Version Control plugin version: 1:15:18
Ubuntu 20.04.4 LTS

Hi!

Since the move to Plastic our team has had a lot of different issues with plastic, but so far the most problematic one is that on occasion, at seemingly random times the entire Assets folder gets removed/becomes private and the person this happens to then has to either undo that change or worse (because undo doesn't always work), reimport the entire project while losing the changes they made.

It has happened on occasion while baking lightmaps, editing/saving prefabs, working with timelines, saving scenes and always happens while Unity is processing/importing files.

Disabling automatic refresh in the Unity plastic options has somewhat helped, but it can still happen at least once a day on some days.

Some minor issues we have include Unity not detecting the installed Plastic SCM app, so the Launch Plastic SCM button in the Plastic SCM tab just opens the pop up asking us to install the cloud edition - which is already installed. We also get a ton of Temp and Library folders being created in our project, the Temp files sometimes contain a ADB-Refresh+Long number folder.

Link to comment
Share on other sites

Hi @JVetulani, I'm sorry that you've been having so many issues with the Version Control package in your project. Unfortunately, the Version Control package does not officially support the Linux platform at this time. Instead, please continue to use the Plastic SCM client as it does support Linux and its various distributions. This is the recommended workflow for Unity users with Plastic SCM on Linux. We will update everyone if our stance on the Version Control package supporting the Linux platform changes.

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...
On 6/21/2022 at 7:07 PM, ryancassell said:

Hi @JVetulani, I'm sorry that you've been having so many issues with the Version Control package in your project. Unfortunately, the Version Control package does not officially support the Linux platform at this time. Instead, please continue to use the Plastic SCM client as it does support Linux and its various distributions. This is the recommended workflow for Unity users with Plastic SCM on Linux. We will update everyone if our stance on the Version Control package supporting the Linux platform changes.

Can you provide a way to disable Plastic SCM in the Unity Editor without removing it from the project or the package list? The team is mixed and some people use Windows some Mac and some use Linux. The list of packages used in the project is synchronised so if one person removes the version control package it will be removed for everyone else which is unacceptable.

In general the whole situation isn't nice to put it mildly because collab was working fine and we were forced off a fully supported solution to one that has massive issues on platforms that are now considered unsupported and do not receive official support when something is fundamentally wrong - I can get minor things like not being able to call plastic from the editor and some such while things are being ironed out and it's a transitional period, but having massive issues like Plastic marking the entire Assets folder as private when you save a scene/prefab or bake lightmaps and not receiving support for it is kind of a big deal for a product we're paying for through the Unity subscription and bought while our platforms were still supported.

Link to comment
Share on other sites

  • 2 weeks later...
I'm guessing if you cloud uninstall the package manager and then manually install it inside the project and not to checkin these changes.
The problem with this is the package version upgrade won't be automatic (we may be able to generate the .unitypackage for you).
 
Another option could be the opposite: the Linux users to uninstall the package from the package manager but don't checkin these changes.
 
Regards,
Carlos.
Link to comment
Share on other sites

  • 5 months later...

Has anything about this changed at all since? 

Baking lightmaps still occasionally marks the entire project as private which makes all the changes done prior to baking lost since you need to undo the Assets folder change, and sometimes the whole assets folder disappears from the Unity project view (while the files are still in the actual folder and untouched...) and requires a full reimport...

I've also noticed something in the project is changing the "current working path" while traversing through the project structure and sometimes creates new Library and Temp folders inside of the Assets (and sometimes an Error that crashes Unity that states that you cannot change the current working path)... It only happens when Unity is processing a large volume of files - like when baking lightmaps...

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...