There is a breaking bug which hampers production for all team members when working with plastic in unity.
Unity: 2020.3.40f1 Version Control: 1.17.2 PlasticSCM: 11.0.16.7460
Issue is very simple, if you save a prefab while the PlasticSCM tab is open (does NOT have to be in focus) in the editor triggers ProjectBrowser.OnGUI.Repaint in very strange intervals. Sometimes it could happen instantly after opening the editor, sometime it happens after you save 2-3 times, sometimes it happens after 5-10 times, but it will ALWAYS happen no matter what without any fault, its a ticking time-bug waiting to happen.
The ONLY workaround that I found which have been implemented team-wide is to NOT have the PlasticSCM tab open in the editor i.e. Rightclick (PlasticSCM) → Close Tab. This solves the issue and this never happens. As soon as you open the PlasticSCM tab, the bug may happen at the prev. mentioned intervals.
While writing this message the message is still up and the editor is not responsive and still stuck.
I searched the forums and found that this bug may have been present and fixed earlier but only for the case of launching the editor where PlasticSCM could get stuck if certain conditions had been met (Not being logged in, loosing internet connection etc.)
However this is not fixed and I have seen no mention of this bug in the forums. This happens for all team members (10+) if the PlasticSCM tab is open.
Thanks for reporting this. Unfortunately, I have been unable to reproduce this behaviour. In the below screenshot, you can see I have created a simple prefab from the Main Camera object in the sample scene, and any changes I make to this prefab are saved automatically and displayed as a change in the Plastic SCM window. Is there something I have done wrong with my reproduction steps?
I used version 1.17.2 of the package as you have reported, but I notice that there is a newer version (1.17.6) available for this Unity version. Can you please update to this version and confirm whether the issue persists?
Issue still persists on Version Control Package 1.17.6
As mentioned in my original post, this does not always happen. Sometimes it happens instantly sometimes it happens after a few tries. This bug just happened because I accidentally left the PlasticSCM tab open and was in the process of moving a gameobject in the scene and pressing Ctrl-S (not modifying a prefab).
Usually the fastest way to reproduce the issue is to (very quickly) make changes and save them without giving the editor time to refresh. This forces the editor to freeze like this. I tried to reproduce this bug multiple times after it having triggered already and I had to force close the editor in task manager but it was not possible to reporoduce. So it may have something to do with executing a specific set of actions before it triggering.
So this just happened as the first thing when launching unity today and saving a change made to a prefab.
It seems like a different process froze up the editor but the behavior is consistent with the previous one “ProjectBrowser.OnGUI.repaint”
I’ve been running into this issue as well. I checked my logs and found an error (pasted below). The exclusive checkout error is strange because my PlastiSCM user is the one whom has it exclusively checked out. I redacted my email in the logs.
PlasticSCM: 11.0.16.7411
Unity3D: 2021.3.7f1
Version Control: 1.17.6
I think this might actually be a thing, I had unity freeze in this same way multiple times after editing two prefabs. And now i’ve edited like 10 with no issue.
It’s of course up to preference, but anything ‘in’ unity is always going to be a buggy mess. I lost all faith with any built-in version control after collab.
I run Plastic SCM externally and find it a far more confident setup, so it’s tracking changes without any reliance on the editor. Not to mention dealing with plastic scm UI in the editor just feels clunky.
This isn’t a solution obviously as it doesn’t fix the built-in plugin; just sharing my experience in using the external version solely, which has been pretty solid.
Unfortunately, attempts at reproducing this have been in vain. Im guessing there is something specific within your lock rules. If you have a reproduction case for this, so that we can attempt a fix, please can you share it with us via a support ticket?
I reported this to our assigned ISS rep who brought this forward to the Plastic team, they were able to reproduce the bug and seem to have uploaded a silent fix (not mentioned in the changelog) with the latest version control package 2.0.1. It may have resolved this issue but I have not tested it extensively to make sure. However I have not experienced any freezes since updating it today.