3 days of PlasticSCM

I simply can't continue to battle through all these ridiculous problems with plastic SCM right now. I've got failed uploads where part of a path is missing that completely restart the update, these issues are not going away and take 45 minutes to popup before cancelling your update entirely. It appears special characters are flagging the failing of paths.

I won't even start with the evil twin issues on migration.

This upgrade has been an absolute disaster had I not had a local backup my project would be a mess. Collbab was great and it worked well. I don't know why you decided to deprecate collab as it was working perfectly and was sooooo easy to work with.

I have not seen anyone from their team answer any posts in the last few days. Are they swamped? I could understand that, but just drop a message on the site or something, instead of ghosting.

Please consider reverting or extending your collab service while they figure things out. I need to continue to work on my project. I have no choice at this point but to go back to manual backups, while paying for nothing.

 

Hi Rafael,

I hope that you understand that I'm simply frustrated so pardon my attitude, it's been 3 terrible days getting this to work.

I'm going through each iteration and manually uploading them as that seems to fix, but I need to wait to get it to trigger in order to see which needs to be done(Edit: Doesn't work). The file sizes aren't beyond that length so I don't know if there is something else happening here. Could it be the length of the upload? My project is over 50GB. However, smaller uploads beyond 5gb seem to also flag errors. This project worked perfectly fine with Collab, so you would think character length etc would have been an issue with that as well.

I'm also on Windows 10 pro.

What is killing me is it's all assets that I've purchased. I typically keep the special characters out of my project but to rename purchases assets is not something I would think is the solution.

 

Some of the errors are from unity build in auto terrain as well. This is part of Unity 2018 terrain conversion upgrades. It does contain some periods and brackets. Do I need to rename every converted file? This is a serious task

 

I don't think bad file paths are going away from Unity's customers (for several reasons such as having a huge amount of casual developers, or developers using asset store assets) so it's something that the Unity plugin for Plastic should scan for and inform the user of these problems.

It's not a one-off so I think some focus is needed on the plastic plugin side.

What do you think?

 

The first step towards fixing this would be to not cancel the entire download if an error occurs. I think I could work around that. This is a paid service it should be close as possible to a mindless thing to run. Just like collab was. It was jaw dropping easy compared to getting new users on GIT.

I don't think the error is related to length but simply how it is named. I did follow those instructions but unfortunately it does not resolve the issue. Again, this is not something an average user is going to start messing around with.



I don't think I want to go down this road to be honest. I'm just not confident I wish to rename all of these files. It will surely bring problems elsewhere by doing so. I've still not even been answered about my build size getting short changed from what I had with Unity and that is an easy fix. They are overwhelmed I'm sure. I'm just going to manually back up for now and give them some time to hopefully update it.

Thanks so much.

 

I used your website forums I did not send an email. Perhaps take your website forums down if you're not answering there?

Anyways, I'm just going to manually update this project for now and wait for you all to fix it. Why don't you just create a new project add in a single file with some ridiculous file name and fix your code to accept the file?