From 371f789adea064475ea2767b8b2e700ed764b821 Mon Sep 17 00:00:00 2001 From: alex Date: Wed, 9 Sep 2026 01:57:45 -0400 Subject: [PATCH] BP: guest released - VM146 restored and hash-verified, hold ended shim.cfg back to hooks=off, binkw32.dll back to the pre-BP file, both autosaves restored byte-identical, game process left not running as found. ad-turn27-two-raiders.sav is deliberately left on disk, so the Load-dialog rows have moved on this guest. --- findings/control-flow/pinned-seed-rich-turn.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/findings/control-flow/pinned-seed-rich-turn.md b/findings/control-flow/pinned-seed-rich-turn.md index 5e9f36f..f255f90 100644 --- a/findings/control-flow/pinned-seed-rich-turn.md +++ b/findings/control-flow/pinned-seed-rich-turn.md @@ -430,7 +430,7 @@ Edits to existing rows: - **Row 415** (AD's oracle row) — append: `PARTLY EXPLAINED 2026-09-09 (lane BP, VM146): with the three AI client seeds pinned, 59 of AD's 94 leaves go away - ModCount, NumFlts, DesignIDs[], FleetIDs[], both build queues, every design and ship record and all four turnstats rows become identical. The 35 that remain are fleets 1970 and 1986 exchanging contents. So AD's attribution "the per-process AI seed" is RIGHT for the substance of the variation and INCOMPLETE: a second, non-seed per-process input orders the fleet-id assignment.` - **Row 326** — append: `And it is not the whole story on rich turns: lane BP pinned it on ad-turn27 and two processes still differed - by a fleet-id transposition and nothing else (2026-09-09).` - **Row 333 / the Rung C row** — append: `C-EXACT FALSIFIED ON A RICH TURN 2026-09-09 (lane BP): restated as "determined up to the assignment of newly allocated fleet ids to newly formed fleets". Damaged, not lost - the assignment is canonicalisable.` -- **Row 62** — VM146: lane BP held it 2026-09-09 01:05-02:0x local for probe 2, and **released it restored**: pre-BP autosaves restored byte-identical from `C:\SOTS\ui\preBP\`, `ad-turn27-two-raiders.sav` left on disk (so the Load-dialog rows have MOVED: with the autosaves deleted the list is **7 rows from y=260 at 29 px pitch, `ad-turn27-two-raiders` is row 1 at (400,260)**), `shim.cfg` and `binkw32.dll` restored to the pre-BP files, main menu verified by screenshot. Left `C:\SOTS\shimdist-bp` + `C:\SOTS\ui\bp{deploy,shot,hash}.ps1` + `C:\SOTS\ui\preBP\`; `click_helper.ps1` untouched. **GOTCHA, AND IT COST THIS LANE FOUR WASTED CLICKS: the lab wall's `/shot/.png` serves a CACHED frame and can be a whole poll cycle (~5 s) BEHIND your last action.** Clicking a Load-dialog row and screenshotting 5 s later showed the row un-selected; a second click showed it selected - which reads exactly like "the click was swallowed" and is not. **Wait ~12-16 s before reading the frame, or take two shots and use the second.** One click selects a row; one click works the OK button. Startup on this guest confirmed at ~2 min (`fg` + `key {ESC}` x3 spaced 2.5 s, then ~90 s); loading the turn-27 save is a further **3.5-4 min** and is not compressible; End Turn on it took **~35 s** with the light hook set. +- **Row 62** — VM146: lane BP held it 2026-09-09 01:05-02:0x local for probe 2, and **released it restored**: pre-BP autosaves restored byte-identical from `C:\SOTS\ui\preBP\`, `ad-turn27-two-raiders.sav` left on disk (so the Load-dialog rows have MOVED: with the autosaves deleted the list is **7 rows from y=260 at 29 px pitch, `ad-turn27-two-raiders` is row 1 at (400,260)**), `shim.cfg` (`hooks=off`) and `binkw32.dll` (`07c96294…`) restored to the pre-BP files and hash-verified, game process **not running, exactly as the guest was found** (CB left it stopped). Left `C:\SOTS\shimdist-bp` + `C:\SOTS\ui\bp{deploy,shot,hash}.ps1` + `C:\SOTS\ui\preBP\`; `click_helper.ps1` untouched. **GOTCHA, AND IT COST THIS LANE FOUR WASTED CLICKS: the lab wall's `/shot/.png` serves a CACHED frame and can be a whole poll cycle (~5 s) BEHIND your last action.** Clicking a Load-dialog row and screenshotting 5 s later showed the row un-selected; a second click showed it selected - which reads exactly like "the click was swallowed" and is not. **Wait ~12-16 s before reading the frame, or take two shots and use the second.** One click selects a row; one click works the OK button. Startup on this guest confirmed at ~2 min (`fg` + `key {ESC}` x3 spaced 2.5 s, then ~90 s); loading the turn-27 save is a further **3.5-4 min** and is not compressible; End Turn on it took **~35 s** with the light hook set. Docs to correct in place (rule 11), proposed, not done by this lane: