I have seen PlasticSCM being mentioned a few times here, I had a rather bad experience with it.
- It won't allow you to update your local workspace without "merge" if you have any changes even if there is no conflict at all
- It won't allow you to submit your changes without a "merge" if the server version is newer even if there is no conflict at all
- Said "merge" takes significant time even if there is no conflict (sometimes more, sometimes less, seems to be pretty random)
- Said "merge" can push you into a merge loop with bigger teams when by the time you are done with the "merging" someone else was faster (e.g. you work remote, people in the office have a huge advantage)
- It has a different "artist friendly" client, but that can't merge at all, and afaik it can't really lock files so it is basically crap
- for the "said artist friendly" client you have to "convert" your workspace, and the two does not work together (at least they suggest not to use both in the same workspace)
- I seriously considered reverse engineering the data because my network usage by their client was ridiculously high compared to the amount of actual data I had to upload/download
- you can "cloak" files, they are basically ignored locally. This would be really cool but it does not work with "merge" - if you have a "conflict" (which isn't a conflict at all in most cases) you will have to download all the cloaked junk which was commited recently. It is especially annoying with branches, because of this updating a branch from main is a disaster
- if I start to upload something, any (fake) "conflict" is only detected after the end of the upload, and I have to do the "merge" client side even when there is no conflict at all