Skip to content

Volumes

Purpose

Restores persisted post-processing onto the preview's rendered global volume.

This territory re-applies saved / imported post-processing settings onto the volume that the preview actually renders, so post-processing survives a window restart.

Owns

  • Post-processing profile restore for the preview volume

Does NOT Own

  • Volume creation or scene placement (owned by the rendering manager; PreviewEnvironmentInstaller installs the rendered global volume and moves it into the preview scene)
  • Volume lifecycle / cleanup (owned by the rendering manager)
  • Volume rendering implementation
  • Pipeline-specific volume behaviour
  • Rendering orchestration
  • Export workflows
  • Panel UI

Allowed Dependencies

Volumes may depend on:

  • Rendering abstractions (IGlobalVolumeManager and pipeline-specific volume manager interfaces)
  • Pipeline volume-prefs utilities

Volumes should avoid: - creating or owning volumes - editor panel orchestration - rendering implementation logic - export workflow ownership

Notes

The rendered global volume belongs to the rendering manager. This coordinator does not create or own a volume of its own — it only restores the persisted profile onto the supplied rendered manager. Restoring anywhere else would land the profile on an off-screen volume the preview never renders.

Pipeline systems own: - how volumes actually function - pipeline-specific rendering behaviour

Future Candidates

  • Keep pipeline-specific logic outside Preview.Volumes.
  • Keep volume creation/lifecycle with the rendering manager, not here.