Question Is Plastic Service broken - Unity white screen

Suddenly, can't open a production project on multiple computers. Just get a white screen with a spinning cursor icon.

Project is U2019.4.32

I'd put in a ticket to support but that usually takes several days....

Also cannot login the plasticscm website with my Unity ID - just get a Server 500 timeout error.

How can we continue to work while Plastic is broken??

Even in the old Collaborate, Unity would still open projects if the service timed out.

Only solution seems to be disconnect from the LAN to force PCM to fail. This should have a timeout value or even be an asynch process that doesn't block the main thread. Do the devs need help fixing this?

WORKAROUND - disconnect from the LAN to force PCM to fail. Then reconnect network. Pretty extreme - but seems to work when PCM is down.

 

Also get this in the editor after applying workaround above.



Looks like the SCM servers are down or the service is unavailable.

 

Same here.



It seems that asia server is currently down.
another victim here (https://forum.plasticscm.com/topic/23340-cannot-connect-to-plastic-scm-server/)
I'm getting this issue all day and I wasted my whole working time of the day. (yes... it is day time at asia east region)

 

Yep, lost of day of productivity here too... Just got a response from Plastic support to say they have been looking in to it and issue may now be fixed.

Obviously they don't have redundant systems.

 

Looks like they are working hard to break PlasticSCM like they did Collab.

This is not the first time this has happened to us either, and as usual....they announce nothing, their status pages are a joke, and it's hours AFTER people report the issues that they even realize something is awry.

 

They still have a bit of work to do to make their service "Highly Available" and "Enterprise-Ready" but I'm sure this was a bit of a wake-up call to their Operations Manager (hopefully).

 

I would have hoped it would have been a wake up call a month ago:

https://forum.unity.com/threads/plastic-scm-down-unity-quality-control.1244554/#post-7920799

 

Same here. I just started using Plastic SCM few days ago. Not very encouraging.

 

Service was down evening of 3/28 and also today. It wouldn't be so bad if it didn't stop the Unity Editor from launching if the Version Control package is installed.

Every time this happens, I get about 100 emails from students whose projects are inexplicably unusable. You can work around this temporarily by eliminating the version control package from the project by editing the manifest.json file in the Packages folder. Remove the whole line that includes the package "com.unity.collab-proxy" and restart Unity.

 

I always advise people to solely use the external/official Plastic SCM software and none of the Unity built-in crap. With it locally stored and not tied in the editor itself, you can obviously still load the project this way.

However, I can also understand with students workflow and inability for them to grab latest workspaces or make commits in any co-operative environment being a significant issue as well.

What a mess.

 

I really encourage unity stuff to make an official statement about this issue, otherwise we are going to believe this is going downhill like several other unity services.

 

I have probably always come off as a pompous jerk on this forum about my complaints about Unity's incompetence (Though people would understand if they saw the lost time and $$ due to these kinds of issues), but instead of feeling happy to be 'right', I am saddened to see long-term proof in the pudding.

The team responsible for collab/plastic should be fired. There, I said it.

They clearly don't take any of this seriously, and have no idea how it affects the teams, the individuals, the implications beyond that, even onward to how it can affect our customers due to these kinds of issues.

I'm a small-time dev compared to some of the folks here, and losing out on builds/source control for hours, or a day at the wrong time is indescribable for the amount of stress it causes me alone.

Compound that with larger studios who cannot resolve a major issue of their live environment project because of problems like this and you are met with losses that can't even be calculated due to rating drops, lost customers/users, paying employees/contractors for time they are wasting on simply trying to access the source code.

I've said it before and I'll say it again. Unity has entirely ruined a lot of the fun in my journey of game development. More time spent dealing with Editor/Service issues than I do on game-dev itself.