Application workflows

Separate Unreal source assets from derived data

Place shared source media in a clear pipeline while preserving Unreal Engine’s own source-control and derived-data architecture.

Give source assets and derived data different jobs

Unreal Engine pipelines contain durable source assets and data generated to make those assets usable on particular systems. Plan those roles separately. Suite can supply shared filesystem access to source media and agreed production outputs on supported hosts, while Unreal's source-control and derived-data systems retain their own responsibilities.

Epic's Derived Data Cache documentation explains that derived data can be regenerated and describes local, shared and cloud arrangements. A shared drive for creative files should not automatically become the location of every cache, repository or running service.

Start with an upstream asset handoff

A practical first use is a common library for approved textures, reference media, renders or other source material supplied by artists. Give each accepted asset a source ID and revision. Record the Unreal project or import task that consumes it and preserve the chosen import settings in the project's existing workflow.

Keep the distinction between the source file and the imported project asset visible. Changing an upstream image does not necessarily mean every Unreal project should immediately adopt it. Let the project owner control that update and its review.

Preserve collaboration and cache architecture

Continue using the project's supported version-control process for project state and changes. Follow Epic's recommended cache deployment for the actual team and environment. Do not assume Suite implements Unreal asset locking, a Zen server or an authenticated cloud DDC service simply because it presents filesystem paths.

Record where temporary work and accepted outputs belong. A machine compiling or cooking data still needs its required processing and storage resources. Streaming source files can simplify access without removing those application tasks.

Test an import and a revision

Have an artist deliver a source asset, import it into a small test project and verify the intended result. Then issue a new source revision and confirm the project owner can adopt it deliberately. Test the actual host, permissions and application behavior rather than describing the pattern as a certified integration.

This keeps Suite's role useful and clear: a shared file layer for production sources across familiar tools. Explore Suite Managed for the asset library and evaluate it alongside the Unreal collaboration and cache systems your team already uses.

Put the idea to work

Start with your workflow.

Bring shared files into your familiar applications with Suite Managed, or connect your own supported storage with S3 Native. S3 Native requires at least 20 TB of active storage.