Using a Shared DDC
Studios should use a shared DDC that all users in a particular location can access. This way, only one person needs to build the derived Asset format(s) and they will be automatically available to all other users. There will occasionally be stalls when Assets need to be processed, but the results are stored and shared. Even on a fairly small team sharing Asset processing work in this way will eliminate most processing time.
It is not advised to copy an entire DDC across the Internet, back up your DDC, or restore a DDC from a backup. This will not do any harm, but it is a waste of time, as it takes longer to transfer the amount of data stored in the DDC than it would to simply generate it from scratch locally.
To set up a shared DDC, override the paths for the
[DerivedDataBackendGraph] (depending on whether you use the binary install from the Epic Games Launcher or compile from source) by declaring the following section in your game's
DefaultEngine.ini file. This section is originally declared in the
BaseEngine.ini where the paths are set to Epic's internal DDC share. Re-declare the section and change the paths to point to a share on your network (e.g.