Figure 3: Offline compilation and runtime application of TileSkipper. The diagram abbreviates the region-count symbol
Kreg as
K . (a) Once per scene, the compiler uses a frozen 3DGS checkpoint and calibration views to measure per-Gaussian pair savings
s and isolated-removal risk proxies
ρ for each threshold level. The backward probe collects sensitivities without updating any model parameter. Gaussians are assigned to eight efficiency-quantile strata
q1,…,q8 (low to high). Within each stratum, Morton ordering and workload-balanced contiguous partitioning produce
Kreg=64 regions in total; Gaussian counts may differ between regions. For region
c and level
ℓ ,
Sc,ℓ=∑g∈csg,ℓ and
Rc,ℓ=∑g∈cρg,ℓ aggregate pair savings and risk. Each penalty
λ selects one level for each of the
Kreg regions. The 48 resulting proposals and uniform-level policies are rendered on disjoint held-out training views. A policy passes only if its minimum per-view teacher PSNR meets
Pmin and its worst-view p99 absolute residual does not exceed
Emax ; among passing policies, the compiler selects the one with the greatest pair savings. Teacher comparisons use the unmodified backbone; p99 is computed from maximum absolute RGB-channel residuals on a fixed
4× spatial subsample. Test views are never used for selection. (b) Each Gaussian inherits its region’s selected level, exported as one uint8 per Gaussian plus a threshold lookup table. At inference, the default threshold is
τg=mgτ0 , where
mg is the selected multiplier and
τ0 is the baseline threshold. Backend-specific handling of opacity caps is described in Section E.1 . The contribution field
ag(x) defines the thresholded support
{x:ag(x)≥τ} . A Gaussian–tile pair is created when the tile intersects this support, using
τ0 for the baseline and
τg for TileSkipper. The dashed blue contour denotes the original support, the orange contour the compiled support, and shaded orange tiles the skipped pairs. Gaussian parameters remain unchanged. The byte and lookup table are read inside tile enumeration, with no per-frame policy inference or additional kernel; projection, sorting, and blending remain unchanged. Footprints, partitions, and table entries are schematic.