I was using Plastic SCM for version control between two computers on the project, they may have had different versions of plastic scm but everything was working fine except checking in was not working in unity plugin (it would show operation has locked workspace) but on both standalone plastic scm it was working. Today I updated plastic scm client to newest on the PC, and now everything has corrupted, showing as added and private. My scene prefabs are broken references, this is terrible as this is a production project and suddently because of plastic scm we cannot continue development.
HI @kevinsyang17 ,
Please make sure you can see the latest version of your code is available in Unity Dashboard.
It might be easier to debug the issue via a Support ticket. Please open a ticket with the support team.
Fuck this, shit happened again fix your app bro
Why the fuck does plastic just randomly make my whole project added and private? The fuck is this rediculous how about you go and open a support ticket I ain’t got damn time to waste on your stupid version control
I don’t have time to manually click the fucking 355 directories to resolve them??
Fixed this shit by going to workspace explore, selecting the root and undo checkout. Then clicked update workspace and waited a goddamn who ass hour.
It seems there is a problem with this workspace metadata folder.
Also, it’s not normal to have 255 evil-twin merge conflicts.
Are you using the Visual Studio plugin or some other plugin?
Do you have some antivirus or external tool that could be accessing to the “.plastic” folder in the root of the workspace.
It seems to be appearing out of random times. I have visual studio but I’m not sure if I have a visual studio plastic plugin? I have Visua; Assist for visual studio, that’s the only one I know I have. I don’t think I have any other antivirus besides basic windows built in (Win 11)
I do have both the plastic scm standalone open and the unity plugin open inside unity as a tab, but most times it work besides the two times it just randomly decided to break the workspace
If it happens again, please attach the content of the “.plastic” folder and also the Plastic client logs:
C:\Users\xxx\AppData\Local\plastic4\logs