When part of an Unreal team sits in Bengaluru and the rest sits in London or Austin, the working day overlaps for only a few hours. Everything that is not written down and checked in before one side logs off becomes a blocker for the other side the next morning. Below is a checklist that helps keep an Unreal project moving when work passes between offshore and onshore developers every day.
1. Make the project open cleanly on a fresh machine
If a new developer in India cannot sync and open the editor without a call to someone abroad, you lose a full day each time.
- Keep a short
SETUP.mdin the repo root: engine version (or the custom engine branch), Visual Studio / Rider version, required SDKs, and the exact sync command. - Pin the engine build. Mixed engine versions across sites cause "this asset was saved with a newer version" errors that nobody can fix until the other office wakes up.
- Commit the
Config/Default*.inifiles and keep per-user settings out of source control.
2. Set up a shared Derived Data Cache per office
Shader and asset compiles are where remote teams lose the most time. A shared DDC on the local network of each office (or a cloud DDC both sites can reach) means the first person to open a map pays the cost, not everyone.
- Point
DefaultEngine.iniat the shared cache and document the fallback to the local cache. - Prime the cache overnight with a build machine so the morning shift is not waiting on shader compiles.
3. Lock binary assets, and say so in the changelist
.uasset and .umap files cannot be merged. If two people in different time zones edit the same Blueprint, one of them loses the work.
- In Perforce, use exclusive checkout (
+l) for binary types in the typemap. With Git LFS, turn on file locking. - Agree that nobody holds a lock overnight without a note in the team channel explaining why.
- Split large levels using World Partition or sublevels so environment artists and level designers are not fighting over one map file.
4. Write the end-of-day handoff note like a bug report
The handoff note is the most important document in a two-site team. A useful one has:
- What changed: changelist or commit numbers, not "worked on the inventory".
- What is broken right now: known crashes, failing automation tests, assets left checked out.
- What the other side should pick up first, with the file or ticket link.
- One question that needs an answer, if any, so it can be answered at the start of the next overlap window.
Keep the template the same every day so it can be skimmed in two minutes.
5. Let the build machine be the referee
Arguments across time zones about "it works on my machine" go away when a build agent compiles, cooks and runs a smoke test on every submit.
- Run at least an editor compile and a cook of one representative map per changelist.
- Run the Unreal automation tests you trust (even a handful) and post the result where both sites can see it.
- Tag the last known good build so the morning team always has something stable to start from.
6. Use the overlap window for decisions, not status
Two or three overlapping hours a day is precious. Status belongs in the written handoff; the overlap is for design decisions, code reviews that need discussion, and unblocking. A 15-minute call with a fixed agenda beats a long, open-ended stand-up.
7. Review the setup after the first two weeks
After two weeks, ask both sides one question: "What did you wait for most?" The answer is usually a missing permission, a slow cache or a lock nobody released. Fix that first.
If you are porting the same Unreal project to consoles later, our console porting readiness checklist covers what to audit before certification.
I work at Juego Studios, a game development studio based in India. If you are planning a similar split-team setup, here is how our Unreal Engine development team works with partner studios.
Top comments (0)