LucasM

Hey @ryancassell any words on this update? I really need it. Just lost 3 hours of work because of .Repaint locking my Unity and not letting me save my scene. And editing prefabs is just painful.

Hi @ryancassell! I'm glad to hear that, but couldn't find the update in the package manager. Do I have to do something? Does it support Unity 2022.1? (which is the one I'm using) Mine is still on v1.15, and I even have Pre-Release packages enabled. I started working on a completely new workspace and I'm still getting the problems. So I'd love to get those fixes.

Hi! The locks are being created right when I edit the prefab and not from a different workspace - I am using cm listlocks to see that this is true. First time I edit a prefab is fine, second time it complains that it was locked. It feels like Unity's plugin is checking against the installed Plastic SCM, instead of working with it. Any ideas what might be causing it and how to fix? My Plastic SCM finds only one workspace, so how is it locking and having trouble with my own locks? Besides the warnings for every single prefab edit, it seems like Plastic is behaving fine when checking in and doing my merges... === Some extra context, plus info on other problems that could be related The problem might have been caused by problems that I had before. I use Cloud and was trying to work Distributed, and was struggling with that as seen in: No owner / created by in change sets or branches - Installation and configuration - Plastic SCM Community I thought I had solved my issues in that topic, but this weekend my automatically created local server license "expired" (which is ofc a bug, and a really big headache, because I had urgent changesets to sync) unfortunately I didn't have time to get help to fix it and gave up working distributed - its support looks a bit clunky/broken by now. My workaround was doing a "clean install" (deleting all I could find) of Plastic then copying files (that I wanted to keep) into a new updated workspace, this time working centralized - maybe this left some conflicting workspace, somehow? Now because I'm directly pointing to the cloud server, I keep getting the locks (which is already annoying, bc we have a few prefabs that get automatically updated by Probuilder and Cinemachine) but the worse problem is that I'm locking against myself with every edit. Adding to that, me and some colleagues working centralized or in Gluon have been getting Unity "randomly" stuck on this ProjectBrowser.Repaint, I have a feeling this might be related to Plastic and, possibly, the problems I'm having (because the fix for other people stuck in this screen previously has also been related to plastic being offline or their account not being connected):

I see, thank you! At least now it's clearer to me how things are working. And although annoying, it's not impossible to live with the different names. I'd just leave the feedback that it's not ideal for cloud users never be able to set their "Owner" names, and not be able to keep coherency between cloud & local names when working distributed. Some solution to this would be a nice to have... Great support btw, thanks again!

Hi @ryancassell! Thanks for the support! To be honest I understood alright the part on how to work centralized (using only cloud), and working decentralized with Sync Views (which I managed to setup and am working already) - I do prefer working decentralized for some reason, probably my Mercurial background. But I feel more comfortable having a copy of the repo in my machine all the time. The part that I didn't understand was about the "On-Premises" user that Plastic created automatically, which I don't know how or seem to have the authority to edit the profile. Is there a way to change this On-Premises user name to match with my cloud user? I just want more consistency in the "Owner" field. This also helps when colouring/filtering, etc. mainly since this problem is not only happening with me in my team.

Upgrading wasn't very smooth. After installing the newer version, for some reason Plastic couldn't connect to my local server anymore (when testing through cmd it said something about not having a license). Then I had to reinstall, then do a clean reinstall, then do an actually clean reinstall to make it work 😅 But I admit the new interface looks a lot nicer! Anyways, now my new change sets are getting an owner again. The weird thing, though, is that I wasn't able to set my workspace with a local repo syncing to a cloud repo by using the "distributed" setup... It was just making a workspace point directly to the cloud. And with the new UI "distributed" doesn't even seem like an option, it just has the "Download Repository" option. I had to make a new repo by hand locally then use Sync Repositories to sync it with the cloud. The weirder part is that now I seem to have a local (On-prtemises) user that I never created, with different credentials: And my change sets have this username as owner, and I can't change it... so it doesn't match directly with my cloud user, which is a bit annoying. And when I try to change the profile I get this. I read somewhere that cloud users shouldn't need to handle this? Am I doing something wrong when setting up the local repo?

Hi! My current installation is at 10.6.16.6479 (which I just realized it's not the latest, I can update to 11 and see how it goes). Only 2 users have been checking in changes for now, through the normal Plastic SCM (with cloud edition), but our users in Gluon also can't see who made the changes. This is from my local repo, but @cloud repo is also having the same issue, it at least can colour by "Replication source" which gives us some hint of who has pushed the change set, but no "owner": Here are the branches, as you can seem, some of them do have owners.

Hi, I've been using Plastic SCM (Cloud) for a while but only now that the team started collaborating more, I realized our changesets have no owner/created by users. Even when I try to "colour by user" the branches, there's zero users to select. That's only happening to one repo, from which we use local replicated from cloud repo. Users won't appear in local nor cloud repositories. Some branches do have assigned owner... but just a few. It's really confusing. Any ideas how to fix this?