erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: Session B dungeon gate user-passed; #344 filed — mid-teleport world-frame race

Browse source 
S1B + S2's shared gate passed live ('Feels good!'), run INSIDE the
dungeon the #344 crash had conveniently saved the character at. #344
filed with its two halves kept separate: the world-frame guard is
CORRECT (it refused a 28.8 km mis-projection — do not weaken it); the
defect is the teleport-recentre ordering race plus the unhandled-crash
failure mode where a deferred retry belongs. AD-64/#324 family.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-07 08:33:43 +02:00
parent ad4a970ec9
commit 42de5f18ff
2 changed files with 34 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

31
docs/ISSUES.md
View file

@ -158,6 +158,37 @@ resolution.
---
## #344 — Mid-teleport crash: world-frame owners disagree during a long portal into a dungeon
**Status:** OPEN — HIGH, user-hit during live play 2026-08-07 evening.
**Filed:** 2026-08-07 (`339-fix-gate.log`, full stack).
During a long-distance portal into dungeon landblock `0x5A48`, entity
materialization threw unhandled on the render path:
`InvalidOperationException: World-frame owners disagree: Runtime centre
(90,72) vs streamed origin (240,126) while projecting landblock 0x5A4801C2.
That offsets the entity by (-28800m,-10368m) from its geometry.` —
`LiveWorldOriginState.EnsureAgreesWithRuntimeFrame:80` ←
`DatLiveEntityProjectionMaterializer.TryMaterialize:166` ←
`LiveEntityHydrationController.ProjectExact`.
**Two halves, keep them separate:**
1. The GUARD IS CORRECT — it refused to project an entity 28.8 km from its
geometry. Do not weaken it.
2. The RACE is the defect: during teleport recentre, the Runtime frame moved
to the destination while the streamed origin still held the source, and a
spawn projection ran in the window. The fix is ordering (defer projection
until the streamed origin recentres, the same family as AD-64/#324's
parallel inbound routes), and the failure mode should be a deferred
retry, not an unhandled render-thread crash.
The user's report ("weenie error 0x04a7") is the crash dialog for this
exception. Same session validated the #339 fix (zero overflows) and the
relaunch logged in INSIDE the destination dungeon cleanly — the race is
mid-flight-teleport-only. Next-session queue: #344, #343, then S4b/S6.
---
## #343 — Shutdown after a wounded render loop: Silk Reset called inside the render loop, exit 82
**Status:** OPEN. LOW-MEDIUM — only reachable after a render-frame exception

4
docs/plans/2026-08-06-collision-fidelity-campaign.md
View file

@ -4,7 +4,9 @@
**Status:** IN FLIGHT — overnight session 2026-08-07 ledger:
S1A (AP-157) closed by measurement, no code · S1B contract ready, not
implemented · S2 contract ready, not implemented · S3 CANCELLED (planned on a
misreading — see its section) · S4 half-landed (AD-65 shipped and USER-PASSED at the 2026-08-07 morning gate; AD-66 withheld
misreading — see its section) · S1B LANDED (b3e43d22, #335 closed) and S2 LANDED (9671af02, AP-155
narrowed), Session-B dungeon gate USER-PASSED 2026-08-07 evening ("Feels
good!") · S4 half-landed (AD-65 shipped and USER-PASSED at the 2026-08-07 morning gate; AD-66 withheld
behind #341's measurement anomaly; AD-69 filed) · S5 closed (fix predated the
campaign; zombie register row) · S6 unstarted · #330 hoist landed, wiring
withheld with a seven-point scope map · #32/#338 pre-work both closed.