Technologies

Unreal content is not text. Maps, materials, Blueprints, skeletal meshes, and sequencers are .uasset and .umap binaries. Git will store them, LFS will shuffle them, and a merge will still be a coin flip. Two people opening the same map is a lost afternoon.

Perforce is built for that file. Exclusive checkout is the collab model: you check the asset out in P4V, everybody else sees the lock and who holds it, you submit a changelist, they Get Latest. No merge tool for a binary. No "I thought I had the latest."

Helix Core also does not pretend a 40 GB uncooked tree is a Git repo with extra steps. Workspaces pull what the stream maps — engine binaries for an artist, full source for a programmer — instead of cloning the universe.

We compile Unreal Engine 4 from source. That build is the editor the team launches, the runtime the games cook against, and a first-class citizen in the depot — not a silent install from the Epic launcher. Engine modules, platform hooks, and game plugins version with the titles that depend on them.

A game changelist is only as good as the engine changelist it was built on. If the editor moves, the content moves with it, in the same Helix history. That is the point of putting a custom engine in Perforce instead of treating UE4 as a black box on each workstation.

P4V is also how the custom editor reaches the rest of the team. Nobody is grabbing a random installed engine and hoping the modules line up. Get Latest on the stream, launch the editor that stream just gave you, work.

Streams keep engine and game from trampling each other. The custom UE4 lives in its own stream. Each title integrates engine drops rather than forking the engine into four silent copies. When an engine submit lands — a module, a crash fix, a cook change — games pick it up on purpose, not because someone copied a folder.

Day to day is P4V, not a terminal ritual. Reconcile offline work. Get Latest. Checkout the map or asset (exclusive). Work in the custom editor. Pending changelist with a real description. Submit. The next person on that map cannot checkout until it is in. History, time-lapse, and diff live on the changelist, not in a chat screenshot.

Programmers submit engine C++ and modules the same way. Artists and designers never have to build the engine from scratch to stay current; the workspace spec gives them the editor binaries from the stream. If they do need source, the mapping is already there.

Shelved changelists cover the "not ready, but I need this machine for something else" case. Submit is atomic: content and the code it needs go together, or they do not go.