Cluster LOD 2c: tolerance controller, per-view error, protection and diagnostics #749

New issue

Closed

opened 2026-10-13 01:57:40 +00:00 by sky_line · 2 comments

sky_line commented

2026-10-13 01:57:40 +00:00

Owner

Part of #642. Wave 2.

One pressure knob: the pixel tolerance (1 px normal -> 2 / 4 / 8 under GPU-time or VRAM pressure); protection by lower tolerance (self / nearest ~0.5 px), not an exemption list.
Per-view error: main view, shadow cascades, reflection probe faces, snapshot resolution.
Hysteresis on cut changes (temporal stability under TAA/FSR).
Diagnostics: per-tier timings, cluster/page counts, A/B line against the old controller; the measurement list on #642.

Rules for this work (all sub-tickets):

Behind RenderVKClusterLOD (default off). With it off, the existing rigged LOD controller (#561 / #613) and every current path are untouched.
Newest path first, chosen by extension presence; every slower path is an additive fallback, forceable on the newest card via RenderVKClusterForceTier.
Failures never crash: a missing page / failed allocation falls back to the coarser parent cut; no unbounded growth (fixed pools, byte budgets, live/cap/peak stats).

Part of #642. **Wave 2.** - One pressure knob: the pixel tolerance (1 px normal -> 2 / 4 / 8 under GPU-time or VRAM pressure); protection by lower tolerance (self / nearest ~0.5 px), not an exemption list. - Per-view error: main view, shadow cascades, reflection probe faces, snapshot resolution. - Hysteresis on cut changes (temporal stability under TAA/FSR). - Diagnostics: per-tier timings, cluster/page counts, A/B line against the old controller; the measurement list on #642. **Rules for this work (all sub-tickets):** - Behind `RenderVKClusterLOD` (default off). With it off, the existing rigged LOD controller (#561 / #613) and every current path are untouched. - Newest path first, chosen by extension presence; every slower path is an additive fallback, forceable on the newest card via `RenderVKClusterForceTier`. - Failures never crash: a missing page / failed allocation falls back to the coarser parent cut; no unbounded growth (fixed pools, byte budgets, live/cap/peak stats).

sky_line added the

labels

2026-10-13 01:57:40 +00:00

sky_line added this to the Slipstream project

2026-10-13 01:57:40 +00:00

sky_line referenced this issue