Post Process Volume Blending And Preview Overlays
What This System Is
Post-process volume blending resolves authored environment volumes into runtime visual effects, transition smoothing, and preview overlays.
How Authors Use It
Authors place volumes with bounds, blend radius, weight, priority, preset gates, optional trigger-forced enabled state, and visual overrides. Preview overlays show the approximate Bevy-side effect, while runtime applies smoothing and dominant visual override selection.
Rules And Invariants
Priority decides conflicts before weighted blending. Blend radius and weight decide influence inside volume bounds. Trigger and preset gates can enable or disable volumes before blending. Dominant visual_override_id should match the strongest active volume.
Validation And Debugging
Overlapping volumes can surprise authors when priority beats distance. Missing overlays usually mean the volume is gated off, has zero weight, or references a missing visual override. Camera/post-process drift points to transition smoothing or preview/runtime mismatch.
Examples
A cave entrance can blend from daylight to cave tint with a feathered volume. If a small high-priority volume fully overrides the cave tint, lower its priority or narrow its bounds rather than changing global post-process defaults.