Plastic has just corrupted my whole OS.
Working as usual this morning, as usual I get my regular Unity crash since plastic has been installed. I’ve tried to turn it off but know it didn’t work as I get plastic pop up warnings.
Well my crash this morning lasted longer than usual. Then nothing would open. I check my file system and everything, the whole of linux was locked out ( small lock in corner of all directories ). I tried a reboot but it only boots into a initrmamf shell prompt.
in all my years of using unity and Linux I’ve never had this. All my problems started with plastics installation. This whole thing is an utter shitshow and a disgrace that people were forced to move over to a not fit gor purpose product.
I’ve managed to recover my file system using fsck disc checking. But this is not on.
Are you using the Linux Unity editor with the Plastic SCM plugin? What Unity version for Linux are you using?
I guess you are not using the Plastic SCM standalone client but the Unity plugin?
I will agree that Plastic on Linux is literally unusable. From corrupting a project to simply not working (uploading/downloading files) it simply doesn’t make sense to use it. Oh well…
Are you using the Linux Unity editor with the Plastic SCM plugin? What Unity version for Linux are you using?
I guess you are not using the Plastic SCM standalone client but the Unity plugin?
Still no change. The plugin for the editor on Linux is still crap. I try to do a checkin, and all it seems to do is to is reimport some packages and reset some settings (like the Odin serializer settings). It seems to checkin some things, but when it’s finished the same items in the UI is checked like it still have changes.
It’s also slow as hell sometimes. And all text, labels, button, menu-entries, dialogs etc. have mostly placeholder text (like e.g. “PrefixUnityVersionControlMenu” for the menu title).
Here’s a screenshot of my project:
I’ve had the same problem last time I tried to use it a few months ago, don’t remember exact version but it as something in the 2022.2 series. I’m now using 2022.3.29f1.
It’s using the Version Control 2.3.1 package.
Perhaps it would work better with the PlasticSCM stand-alone program? Even if it defeats the purpose of having the plugin in the first place.
Update: Yes it seems to work better in the PlasticSCM stand-alone tool.
Update 2: The plugin had managed to corrupt the project, so all asset sub-directories were considered empty. Solved that by removing the “Library” directory in the project root, and starting Unity again. Some assets were still messed up, so I had to reimport them.
1 Like
The Plastic SCM standalone client is tested and officially supported in Linux. I think you should be ok if you use it in the future.
I’m afraid the Version Control plugin for the editor is not officially supported in Linux.
