Originally posted by Lawlcat
View Post
A little late to the party, but the trouble is the tradeoff between a small packaged build and rapid iteration. Usually the smallest build is going to require cooking content and then pak'ing it up. This gives you the executable, configs, cooked content. But cooking takes time, and you have to maintain two binaries (the editor and the MyGame.exe).
If you don't cook, then you have to copy all content and only maintain one binary, but identifying WHAT content can be tough (Fortnite is huge for example), so you copy it all and that can be gigs.
I use Robocopy and its "only copy new files" so I only take the big hit every once and a while. It would depend on your content churn.
The syntax is like so (use Robocopy /? to see details)
robocopy <dir> \\%MACHINE%\YourOutputDir\Engine\Binaries /mir /w:1 /r:1 /ndl /nfl
Leave a comment: