Ridge baker: G-buffer cards from seams through the ray march (chain painter deleted) #170
Loading…
Reference in a new issue
No description provided.
Delete branch "void/ridge-gbuffer-baker"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Cut
ratatoskr-backdrop:cut_spec:cut-ridge-gbuffer-baker.r2. Reports h1 to h3; Soul verdicts s1 and s2.The baker no longer paints stage flats from peak chains. Each place authors an ordered list of split depths (
card_split_km; Vienna [6, 40]). Seam searches with forward energy move each split per column into a depth gap. Each card is a layered-depth G-buffer of the terrain visible beyond its near seam: albedo, normal at the hit (across neighbouring rays at equal distance, scaled by the authored exaggeration) and log-distance. Cards are written as colour and geometry WebP with manifest v2, and the runtime lights them live.Rulings:
ratatoskr:ruling:ridge-bake-gbuffer-depth-bands,ratatoskr:ruling:ridge-cards-runtime-lit,ratatoskr-backdrop:ruling:ridge-card-splits-authored-any-count,ratatoskr-backdrop:ruling:ridge-cards-per-card-slide,ratatoskr-backdrop:ruling:ridge-cast-shadows-dropped-for-now.sun.pyandmutate_export.py.mutate.pykills 27 of 27 (Yggdrasil). Soul's encode round trip, receding-ridge seam fixtures and normals checks are pinned.public/andsrc/. The served backdrop does not change until the runtime cut lands.ratatoskr-backdrop:follow_up:ridge-card-reveal-mask-in-runtime-contract). Commit 1 of the mask deletion does not build; the next commit fixes it.🤖 Generated with Claude Code