From 9ba0c3eb62f8e58fcdae45d221a85b162ab7e612 Mon Sep 17 00:00:00 2001 From: Anne Jan Brouwer Date: Sun, 30 Aug 2026 21:57:48 +0200 Subject: [PATCH 1/3] docs: verify the local fork checkout against the rev Cargo.lock names --- OPTIMIZATION-BACKLOG.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/OPTIMIZATION-BACKLOG.md b/OPTIMIZATION-BACKLOG.md index 6b16470..6b80e0d 100644 --- a/OPTIMIZATION-BACKLOG.md +++ b/OPTIMIZATION-BACKLOG.md @@ -48,7 +48,8 @@ props stay on the serial path (async asset load, no CPU sampling). Startup wall- predicted (record/shot builds were already inline; live windowed loads benefit). 171 tests green. ### Fork-shader batch (`../bgs-fork`, branch `martin-tightcut`) · the full clone→edit→A/B→push→repoint dance -Confirm the local checkout matches the pinned commit (`Cargo.lock` rev `f94855a4`); then path-patch +Confirm the local checkout matches the pinned commit (whatever rev `Cargo.lock` currently names — it +moves with every fork bump, so read it, don't trust this line); then path-patch martin to `../bgs-fork`, edit, rebuild **sh0 AND sh3**, A/B both, push the `martin-tightcut` branch, repoint the git dep + `cargo build` (re-resolves the lock to the new rev). - **#5 — dead-discard + alpha early-out** (`gaussian.wgsl:705-707` `dist²>9` never fires; ~21 % of every From 97cc0424532511f62cb5b3a1f8d67fbc7a2c7d13 Mon Sep 17 00:00:00 2001 From: Anne Jan Brouwer Date: Sun, 30 Aug 2026 21:57:55 +0200 Subject: [PATCH 2/3] docs: #237 landed after the 8.0.1 bump, so it is not in the published 8.0.1 --- DESIGN.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/DESIGN.md b/DESIGN.md index cc5c53d..7d8377e 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -726,7 +726,8 @@ slot itself is a fresh open item, added to §9.2 #16). > **shockwave** (transition mode 8), **morph_stagger** (§8), a tighter synthetic-content quad extent > (§9), an **additive/emissive blend mode** (§10, `MARTIN_ADDITIVE`), and the > `lazy_type_alias` → `checked_type_aliases` nightly-gate rename (§11, keeps the crate building on -> post-2026-07 nightlies) — which has since gone **upstream** too (merged as #237, shipped in 8.0.1), +> post-2026-07 nightlies) — which has since gone **upstream** too (merged as #237, which landed *after* +> the 8.0.1 version bump, so it is on upstream `main` but not in the published 8.0.1 on crates.io), > so §11 is now a docs-only entry. The sort speedup (§3) likewise went > **upstream** (merged as #229; #231/#232/#233 are further upstream fixes). The authoritative, current list is the fork's > **`CHANGES.md`**; this section is kept as the original design sketch. The deeper WGSL/Rust plumbing + From ea73ccdacc21468330d72de12e29a05c1404c1c8 Mon Sep 17 00:00:00 2001 From: Anne Jan Brouwer Date: Sun, 30 Aug 2026 21:58:05 +0200 Subject: [PATCH 3/3] docs: drop the fork skew note, the branch is fast-forwarded --- Cargo.toml | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index 57ae9df..fced3bc 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -118,10 +118,9 @@ strip = false # `cargo update` — can't silently repoint the engine's renderer to unreviewed commits before a deadline. # To pull new shader edits: push the fork branch, then bump this rev deliberately (+ `cargo update -p …`). # -# NOTE (2026-08-30): this rev is the §1–11 edit set REPLAYED onto upstream 8.0.1, which currently lives -# on the fork's `martin-tightcut-rebased` branch — `martin-tightcut` itself still points at the 8.0.0 -# base. Verified identical: replaying `martin-tightcut` onto upstream/main locally reproduces this -# commit's tree byte-for-byte. Fast-forward the canonical branch when convenient — -# git push --force-with-lease origin ffaecd70…:martin-tightcut -# — and do NOT delete `martin-tightcut-rebased` before that, or this pinned rev becomes unfetchable. +# `martin-tightcut` is at this rev (fast-forwarded 2026-08-30); the pre-8.0.1 base is kept on the fork +# as `martin-tightcut-8.0.0-base`. A local `../bgs-fork` checkout must be at this rev or newer: cargo +# does NOT error when a `[patch.crates-io]` entry fails the version requirement — it warns "patch was +# not used" and silently resolves the crate from crates.io instead (real upstream, none of our §1–11 +# edits), and the build then dies on missing CloudSettings fields with the cause scrolled off-screen. bevy_gaussian_splatting = { git = "https://github.com/annejan/bevy_gaussian_splatting", rev = "ffaecd70f5102934beaca58845d3d2299b73394a" }