Loading video...
Video Failed to Load
Developers sometimes ask me if they should use Git with Unreal Engine projects. This is my response to that, I give you my "Git rant" 😅 #uetips This is a short clip from "Lessons Learned From A Year of Unreal Engine AAA Development":
12,123 views • 1 year ago •via X (Twitter)
11 Comments

I have lots of other presentations about Unreal Engine development, I've collected links to all of them at check them out!

For a pure coding standpoint, I dislike P4. Iterative work, working on the same file for different purposes is a nightmare with P4. And everything is server based, no local work. But for. asset management, yeah it's better. I know it's a pain, but perhaps code:git & asset:P4?

I've seen studios try that, it has its own can of worms of course with keeping things in sync but can work well enough, they did ship their product! But two studios I've been a part of who tried it moved away from it to a single VCS system. Maybe for a reason 😅

Unreal Git users rn

Since I started to use Perforce, I can't go back 😆 But I still use it for game jams

Perforce or bust, it's arguably more involved in the setup and most people aren't as familiar... But once you have a workflow set you can have a team working on it without it making you want to run a fist through your monitor

We use perforce and UGS with the simplest setup possible, but people definitely over think this… the secret to source control is == use source control!!! Unreal has a great p4 integration (crashes quite a bit on macs) and it’s a pleasure to collab!

Use svn with it. You can branch. And lock things.

Yup, I'd recommend SVN, Plastic SCM, or P4 over Git for UE teams. Although P4 does have the advantage of allowing you to push without being on the newest commit, which becomes surprisingly essential for bigger teams where commits are happening all the time.

That's great and all but it's impossible to convince smaller studios (ones that barely go over the free threshold) to buy into P4 - it can be prohibitively expensive. I like SVN personally (for the editor integration) and that's often an easier sell with Assembla.

Yup, I recommend SVN over Git for teams on a budget.

