Can you attach the Plastic client logs?
C:\Users\xxx\AppData\Local\plastic4\logs
Can you run the following command on a cmd and share the output?
cm iostats YourOrganization@cloud --nettotalmb=128
If you are connecting from a slow network, I would recommend you to enable these settings in the “C:\Users\xxx\AppData\Local\plastic4\client.conf” file. It should prevent the issue to happen again:
Add the following lines to the client.conf (Located here C:/users/user/appdata/local/.plastic4 on windows and User/.plastic4 on Mac):
We just released a fix for an existing checkout locking the workspace in Version Control v1.16.0 (for Unity 2019) and v1.17.0 (for Unity 2020+). Please download it from the Unity Editor’s Package Manager and see if that resolves your issue.
Hi @Ryan-Unity , just wondering whether there is a plan for the fix to be released for Unity 2022.1? I see only 1.15.18 version in the package manager.
Hey, I’m using Unity 2019.4.40f1 and my latest version of Version Control seems to be 1.14.18, and I’m also having this issue. I’m trying to fix it by updating but I can’t seem to be able to.
Is it possible to disable Plastic integration without uninstalling the package, but still utilize the external Plastic GUI? The reason is because I’m working with a large team, and some members prefer the integration, and others prefer the external GUI, but one user removing the package would get synced across the repo.
Hi, thank you for the reply. Unfortunately, this method would not work for our team, as we have several important packages being used and we must keep everybody’s packages and manifests synced at all times. I’m looking for an option to simply disable all calls to the Plastic workspace from within Unity. It’s a bit alarming that attempting to do so by turning off Version Control just destroys the entire workspace.
OK. Updated the Version Control package.No dice. I am locked out no matter what. I got forced onto this Plastic SCM. It has not behaved properly since day one. Every time we saved something in the last month or two Platic SCM contacts the server and crashes the app. No I won’t send you a build I have too much work to complete and this already puts me behind the 8 ball. I am not doing quality control for Unity and the company I am contracted to as well. They did not hire me for that and I do not get paid for that. I think every one of you should split your paychque and give it to those who lose a days or weeks pay to shoddy integration on your part. Two PC’s and a Mac cannot upload, download or work due to this crap and I have been at this a few hours already. I get two main errors. The first when I try to upload and it is locked because something is checked out… Nope…nowhere. We have rebooted and tried the whole gamut and nada. The second is trying to go back to a changeset and it says i must remove a file from my Assets which DOES NOT EXIST.
So… trying to get around the lockout I create a new project and link to my org. Then Plastic SCM acts like I do not have an account. No place where I can link to the project to download it like in Collab. Just nothing…nada…no clues. Then I click away from the Plastic SCM window and go back to click it and it disappears and is now greyed out in the menu. Nothing is happening like it should if software is developed properly. If I want to overwrite a damned change i should be allowed to The repo is mine and not Plastic SCM’s. Plastic SCM has no right to dictate what I can do with a file…unless I am forced to use them,. Since I am forced then they should make sure it works for Unity devs and give me the option to override your control freakiness… Money is hard enough to come by and you have me off the clock bug tracking your crappy software. Sorry for not being polite but this is tiresome from day one and has not saved me any time and has indeed cost me about two weeks of lost time so far.
This whole “Plastic” “SCM” “Migration” thing has been everything I dread as both a user and now a developer, and it’s really superlative at that. I cannot imagine a worse or more obstinate UX experience trying to upload a file than what I’ve recently encountered with Plastic SCM –
it’s utterly bipolar.
I won’t hear from it for two weeks about any kind of uploads or diffs or replacements or overrides I’m doing, and then all the sudden last night it takes me 8x as long to upload footnotes in scripts while I’m looking for my intellisense in a project with a bunch of conditional compile directives that only autocomplete on certain workstations I use.
In weeks prior I would have smooth running until I was in playback just after an upload and I guess the handshake for plastic looking to finish up my file indices after checking in is enough to crash unity 33% of the time. Then that was gone for a few days, and now this episode.
I now have to close both Unity and VS2022 in order to allow my other workstation to upload a script once I’ve “checked anything out”, it won’t let me merge scripts when my older script is only different by “//” and threatens a big fat hullabaloo about needing to recompile my grandmother’s emigration records. It won’t let a 2500 file rollback attempt run through because a single index file doesn’t exist deep in a directory; Collab didn’t act like this, it would have just downloaded the cloud copy from the project repo or rolled past it and restored everything else.
Anyway this is ludicrous it’s an all-timer, I’m on hour 4 today of processing the little meddling details of what Plastic took us through this morning and now we have all these splintered project versions we have to clean up thanks to simple auth and handshake errors and unnecessary directory polling at runtime - not to mention poor cooperation with VSCode’s typical monitoring of Assembly-CSharp. Plastic seems to tug of war with it and I get no movement out of my reload assemblies progress bar til I either quit VSCode or Start it back up - then plastic starts relisting cached files like I made edits when I didn’t. I’ve watched it.
You have to hit undo changes like 8 times on all selected files to get the list back to truly no changes from last checkin. Marvelous!~
And… you have done it to me again. I made an entirely new project. I downloaded the repo. I updated incoming changes. I went to upload and it tells me I am locked out again. Will not let me decide what I want to overwrite. Nope…another few hours of mucking about only to have it happen again. This should not be Groundhog Day by my calendar. Jeesh. Get it together folks.
What is your plugin version? I want to be sure you are using the very last Version Control package version: 1.17.1
The issue reported in this thread was fixed and we are not aware of any major issue after this upgrade.
If you are still facing this issue (or some other issues according to your last comments), please open a ticket at support@plasticscm.com and we will arrange a meeting with you to review your workflow and issues in detail.
