Camouflaj는 Helix를 사용하여 향상된 속도와 안정성을 보여주었습니다

Camouflaj's problem? Their former tool couldn't keep up. Why? The art directory alone is over 100GB, a large part of its repository consists of binary files, animation files are 100MB on average, and up to 20 percent of the team works remotely. 

즉각적인 비지니스 효과

빠른 결과물

하루에 2시간 이상 인력 또는 1년에 12,000시간 인력 절감

파일 잠금

팀원이 잘못된 자산 버전에서 작업 할 때 발생할 수 있는 주요 생산성 손실을 방지합니다

향상된 가시성

팀원은 누가 어떤 자산에서 작업하고 있는지를 알게 되어 보다 효율적으로 작업할 수 있습니다

Mercurial사용하는데 있어 속도 문제가 크게 있었습니다.

그래서 Helix를 체험하기로 결정했습니다. 밤과 낮 같은 차이였습니다. 결과물이 30분에서 1분 미만으로 하루에 약 2시간의 인력을 절약했습니다. 말씀드리기 충분합니다. 저희는 바로 바꿨습니다."

Case Study Body1 Camoflaj
The Camoflaj Team via


Camouflaj's team of 25 that includes artists, designers, developers, and production personnel working on République needed to find a better solution to collaborate on artifacts that include code, art, and Unity game engine assets. The problem? The art directory alone is over 100GB, a large part of its repository consists of binary files, animation files are 100MB on average (and can get up to 1GB), and up to 20 percent of the team works remotely at any given time. The tool they were using simply couldn't keep up.


Core Pain Points

Before Helix Core, Camouflaj’s version control system, Mercurial, was slowing down the development pipeline:

  • Mercurial’s peer-to-peer architecture caused collisions between users, even when those users were submitting different files. Users might be required to resubmit files that they had not worked on
  • The system would slow down drastically when handling binary files. At times, users would have to submit multiple times
  • Merging was difficult to complete

“Initially we thought that not having a central server would create a better workflow,” says Ryan Fedje, Senior Game Designer at Camouflaj. “However, the result was that it could take half an hour to get a change submitted at the end of the day.”

Why Helix Core?

Camouflaj briefly evaluated Git and Subversion before deciding on Helix Core. Helix was attractive because, unlike Subversion, it would not generate extra files that would waste storage space. Fedje and others also had previous experience with the product.


Proof of Concept

Running Helix Core alongside Mercurial during a trial period, the production team saw a dramatic difference: submits immediately went down from half an hour in to under a minute.

“We have found Helix Core to be incredibly stable,” notes Vincent Loiseleur, Technical Designer.

  • Camouflaj set its server to have two network cards for direct routing to Helix Core
  • Team members check files out of Helix Core and keep them locked while they are doing their work, avoiding conflicts with other users
  • The Helix Core plug-in for Unity has made it faster and easier to author content in Unity
  • Software release managers can assemble projects using familiar engineering processes, and Git developers can continue to use their preferred tools
  • Unix build scripts access the Helix Core repository to generate builds as often as 20 times per day. Getting all of the code from Helix Core takes less than five minutes


Expanding the Footprint

Moving forward, Camouflaj is looking at ways to incorporate additional Perforce products into its development process, including Helix Swarm, and P4GT, the Helix Plug-in for Graphical Tools. According to Loiseleur, “Helix Core offers us a wide array of tools and modules that I can see improving our workflow here at Camouflaj and we're only just starting to use a fraction of them.”


➡️ try Helix Core