After using Git and Git LFS for a few years for game development, we were looking for alternatives - the way Git handles binary files even with LFS is a bit cumbersome, to say the least. PlasticSCM on the other has been designed with binary-files in mind from the get-go, and the support for binaries is really good and it just works the same as with text files (diff is of course a bit different case, but out-of-the-box image diff support in Gluon helps a bit, and you can use any diff you like for files).

After getting used to, I have also come to like the way PlasticSCM handles DVCS - you commit straight up to a repository, but that repository can be local. The local and remote repositories are then just synced up. Kind of like git, but still different - in git the local repo is handled inside the project tree, but in PlasticSCM you basically setup your own PlasticSCM repository server which is used for committing (although this process is painless and you won't even realize it in the install program).

Great GUIs (there are two, a DVCS PlasticSCM gui and Gluon, the straight up commit to remote gui intended for artists), and commandline support help a bunch. Review collected by and hosted on G2.com.

The GUI was really confusing at first, and even now the fact that multiple tabs open when opening the exact same view opens a new tab, which is annoying. As the concept is similar, but still different to Git, it took a while to get to grips on how the whole DVCS idea works in PlasticSCM - the docs helped a bunch though. Review collected by and hosted on G2.com.

Fast, with the ability to be true distributed, central, or anything in between, but also with features enterprises look for like built in ACL security (at the repo, branch, and path level), LDAP authentication, and great component support. Review collected by and hosted on G2.com.

Really it is hard to find something major to dislike. Closest I can come to it that there are not enough other people using it...yet. ;-) Review collected by and hosted on G2.com.

Plastic SCM is mostly visual tool that makes it easier to jump into and makes it easy for everyday use. Review collected by and hosted on G2.com.

Sometimes setting up repositories (local/cloud) and knowing what type of repository or sync type to use can be a bit confusing. GLUON is a bit too simplified and we haven't really found a use for it yet. Review collected by and hosted on G2.com.

Plastic SCM makes it very easy for new users to become proficient. The menus are very intuitive and there are not too many of them. It gives you exactly what you need and not much more. We have rolled out to large 100 person teams at multiple sites with minimum impact to productivity. And we got compliments on the tool we chose. How often does that happen? Review collected by and hosted on G2.com.

I am very happy with the support we receive from Codice Software. If there is one thing they could do better it would be offering a global concurrent license. There are no tools to determine if a user is still using the application and no reporting to determine trends in use. Review collected by and hosted on G2.com.

The intuitive UI, the easy merging and diffing, (BLUEPRINTS DIFFABLE!!) Review collected by and hosted on G2.com.

the lack of a custom theme editor, the lack of the ability to make post it notes or paint scribbles on the branch explorer Review collected by and hosted on G2.com.

There are several features. Its fast. Its distributed if you need it. The branch explorer gives a great overview of the project and its multiple branches being worked on, and highlights "lost" unmerged work. Semantic merge to deal with code that just moves around at the same time as other changes. Its friendlier than GIT and easier for teams to switch to, from traditional source control products. Supports GIT repos. Review collected by and hosted on G2.com.

Only issue I have is that the agile nature means that new features and fixes get rolled up in the releases. As as large team we want stability, and to control when new features are rolled out. Management of multiple respositities is limited to 1 level and a bit crude. When working distributed, developers can forget to merge back to the build server. Review collected by and hosted on G2.com.

The simplicity of interface, functions offered is the highest praise as compared to other VC options. Review collected by and hosted on G2.com.

Although SCM and Gluon's power resides in it's simplicity for usage, I miss branching options of git. Review collected by and hosted on G2.com.

The interface is friendly, the use is simpler than with other version control systems and the properties included in the branch search are quite useful. Review collected by and hosted on G2.com.

The interface of conflict resolution is not very intuitive, access to some properties, such as accessing the history of a file, is not always easy to find Review collected by and hosted on G2.com.

It's a robust program, it can take control of several repositories and also search for versions of a developed program during years back. It also has a very useful timeline of any created branch with their version along with a time tag. Mostly you'll use to create branches, merge with other branches and look out for controlling parallel developments. Review collected by and hosted on G2.com.

The program is not very stable, when it works it's magnificient, but when it's not you'd like to have a few words with the creators because sometimes you can go crazy, for example any empty branch points to the source but any change and the graphical disposal of elements is suddenly the opposite as it was a few moments back. Review collected by and hosted on G2.com.

I love the way Plastic is managing branches. I fits perfectly with the way our company works. We are using Review collected by and hosted on G2.com.

Hard to say, all th eproblems I had in the past are already solved (Thank you customer service!) Review collected by and hosted on G2.com.