Depth composition¶
For usage and limitations, see Gaussian splatting.
Render passes and either Gaussian backend shall be composable in either order with an optional shared per-path depth attachment. Without an attachment, rendering shall retain its color-only behavior. |
Each rendering stage shall independently enable or disable depth testing and depth writing. Testing shall reject contributions behind the existing surface; writing shall update the depth for subsequent stages. Disabling writes shall leave existing depth unchanged. |
Both Gaussian backends shall support accumulated-opacity and nearest-opaque-splat depth, with a configurable opacity threshold. The default shall be accumulated opacity on compute and nearest opaque splat on raster. Depth export shall be optional and independent of the shared attachment’s testing and writing controls. |
Each execution path shall have independent depth storage. A shared attachment shall clear once per graph execution by default, with optional preservation between executions. Mismatched color/depth extents or path counts shall be rejected. |
Compute splatting reads GPU buffer snapshots; raster splatting uses native read-only depth testing. Gaussian surface updates use GPU-only transfers. The graph orders snapshots after the preceding color producer and attachment updates after the depth calculation. No per-frame CPU readback is used. |
Raster accumulated-opacity depth is computed by a depth-only compute pipeline; nearest-splat depth uses fragment atomics where supported, with a compute fallback otherwise. Each method is an approximation to a translucent surface, so different rendering orders need not give identical translucent blending. |
Checks nearer and farther opaque geometry in both rendering orders, with both Gaussian backends and both depth methods. |
Disables testing and writing separately and verifies the resulting occlusion. |
Reuses compiled graphs with moved Gaussians and two paths, verifies clearing and independent color results, verifies explicit depth preservation, and rejects mismatched attachment extents and path counts. |
An overlapping translucent stack has an accumulated-opacity surface and no individually opaque-enough splat, with the same selected method on either backend. |