Shared ddc namespace for multiple project and engine version

Is it safe to use a single derived data cache namespace for multiple project and multiple engine version? Can it cause any cache ‘interference’ between projects that may lead to engine instability?

[Attachment Removed]

Steps to Reproduce

  • We have multiple animation\tv show projects using Unreal Engine 5.7.
  • One of them has been migrated to UE 5.8 recently.
  • All of the projects are using the same namespace for local and shared ddc (zenserver).
    [Attachment Removed]

Hi,

I would also like to query it’s relation to Asset Virtualisation. We do frequently run into issues where artists would copy files from one project to another (instead of using Migrate). These files seem to work for the user that made the copy as they seem to have a local cache. But for another artists, it does not work.

Just curious if splitting out the zen namespace can cause the original user to run into the Virtual asset error?

Thanks,

[Attachment Removed]

I have another follow up question around the shared ddc.

When we switched our projects from 5.7 to 5.8, we noticed that the File System cache is back. Our assumptions were that Zen would replace the File system cache?

Please see attached screenshot

[Attachment Removed]

Yes, we normally run within Epic with multiple branches of varying engine versions sharing the same DDC. The key setup for DDC is meant to ensure that even across engine versions, things share data when they should and keep different data when they should. People can make mistakes at this, but that’s the intended goal.

Regarding the follow-up about the File System cache - that’s an unintentional bug and I just submitted a config change that should reach a future 5.8 patch release that will correct that by removing the File System cache layer. Thanks for reporting this.

[Attachment Removed]