Perforce Helix Core

Helix Core is a centralised version control system built for repositories that Git handles badly: multi-terabyte depots, thousands of large binary files, and teams where artists and designers commit more bytes than programmers do. It provides exclusive file locking so two people cannot both edit an uncompressed texture or a level file, a streams model for branching, and proxy and edge servers so studios in several locations are not all pulling from one machine over the internet. Unreal Engine ships with direct Perforce integration, which is a large part of why it became the default in console development. The commercial catch is the shape of the free tier. Helix Core is free for a small handful of users and a small number of workspaces, which suits a programming team and does not suit a game studio, because the people generating the assets that make Perforce necessary are artists, animators, designers, audio staff and outsourcing partners. The moment the whole team needs access, you are on quoted per-seat pricing renewed annually, and the seats that push you over the threshold are exactly the ones that only touch the depot for one milestone. Perforce does not publish that pricing, so a studio cannot budget the transition without a sales conversation. Studios buy it because the alternatives fail at their scale, not because they enjoy it. The trade-offs are real: it is centralised, so losing the connection to the server stops work; it requires an administrator who knows Perforce; and programmers arriving from Git find both the model and the tooling alien. None of that changes the fact that at fifty artists and two terabytes of assets there is very little else that works.

• 

  Perforce Helix Corevs

  

  Unity

  Unity: Unity Version Control covers the same asset problem inside an engine already licensed