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

docs: record failed owner gate and bounded #477 validation recipe

Browse source
This commit is contained in:
Erik 2026-09-05 11:18:16 +02:00
parent de427d2c02
commit 8fd5e434b6
7 changed files with 422 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

74
docs/ISSUES.md
View file

@ -39,6 +39,61 @@ confirmed closed by the owner, 11 need a focused live gate, and 43 are safe to
remain closed. See
[`docs/research/2026-08-28-owner-closed-issue-validity-audit.md`](research/2026-08-28-owner-closed-issue-validity-audit.md).
## #481 — Low initial FPS after entering the world
**Status:** OPEN, owner-reported during the `de427d2c0` gate on2026-09-05.
Owner felt FPS was initially low on world entry. No numeric FPS/frame-time
capture was taken. Measure initial versus settled CPU/GPU frame percentiles,
streaming/retirement debt and allocation on the same High/4xMSAA profile;
do not label this fixed by #475 or reduce visibility/quality to conceal it.
Evidence: `research/2026-09-01-overhaul/475-owner-regate.md`.
## #480 — Wielded hand equipment is invisible
**Status:** OPEN, owner-reported during the `de427d2c0` gate on2026-09-05.
Owner reports nothing wielded in either hand is shown. Attachment messages
exist in the session log but do not prove render membership or draw admission.
Trace exact root/child identity, canonical CELLARRAY propagation and the
production draw consumer. No parent-cell fallback or duplicate membership owner.
Evidence: `research/2026-09-01-overhaul/475-owner-regate.md`.
## #479 — Hanging Rynthid structure partly shifted after recall
**Status:** OPEN, owner-reported during the `de427d2c0` gate on2026-09-05.
The owner reports the hanging Rynthid over the crater is partly shifted after
Rynthid recall. Exact object/part identity and cause are not yet established;
do not assume wrong collision placement, streaming origin or Setup transform
without reading the real asset and production transform path. No screenshot
was supplied in this round. Evidence: `research/2026-09-01-overhaul/475-owner-regate.md`.
## #478 — Dungeon lighting too dark, especially Town Network
**Status:** OPEN, owner-reported during the `de427d2c0` gate on2026-09-05.
Town Network was barely visible; the run includes indoor00070143. The current
High-profile indoor authored-light/material path needs comparison with retail.
#469's outdoor direction fix does not establish indoor correctness. Do not
blindly raise global ambient or change the owner's brightness settings.
Evidence: `research/2026-09-01-overhaul/475-owner-regate.md`.
## #477 — AMD watchdog / Vulkan device-loss crash while jumping in Neftet
**Status:** IN-PROGRESS, crash independently confirmed2026-09-05 on clean
`de427d2c0`. Owner saw an AMD crash notice while jumping around Neftet.
stderr records unhandled ErrorDeviceLost from the abandoned-frame timeline
submit; shutdown also fails waiting for frame serial37509. Windows .NET1026,
ApplicationError1000 for exact PID26920 and LiveKernelEvent141 corroborate it.
The stdout graceful-logout lines are cleanup, NOT successful process exit.
RX9070XT, reported Vulkan1.4.349/driver2.0.395, final1600x900, High/4xMSAA.
First raw acquire result is not retained: the swapchain adapter collapses
fatal failure and ordinary unavailability to false, then the empty signal
submission reports device loss. This is a diagnosis-obscuring boundary, not
proof of the initiating GPU fault. No premature-release or semaphore-reuse
cause established. Keep first-failure evidence distinct from secondary teardown.
No driver replacement, TDR-delay changes, skipped waits or forced recovery.
Exact stack, hashes, local Windows report and limits:
`research/2026-09-01-overhaul/475-owner-regate.md`.
## #476 — First post-resize graphical gate PNG is horizontally corrupted
**Status:** OPEN, observed2026-09-05 during #474 regression; capture-lifetime
@ -61,7 +116,19 @@ and real first-frame/resize validation follow #475, not inside its chunk.
## #475 — Debt-free collision retirement yields a frame per prefix
**Status:** IN-PROGRESS, lead bounded contract2026-09-05; no fix landed.
**Status:** REPAIR LANDED + REVIEW-CLOSED at `de427d2c0` (2026-09-05).
Lead independently verified Release 0 warnings/errors, Runtime 1,891/1,891,
Headless 48/48 and App 297/297. Retail review's test-only findings were
reconciled in one fix round; production/lifetime review 2 PASS. Exact
eleven-file reviewed return `ab989d717` matches the integrated Git blobs.
Manual owner re-test completed five reveal generations with zero reported
reveal failures. Owner narrowly accepts recall timing ("seems ok"); exact
nine-hop benchmarking remains owed. Overall gate FAILED on #477–#481,
including a confirmed device-loss crash. Logout cleanup is not clean exit.
Evidence: `research/2026-09-01-overhaul/475-lead-verification.md` and
`research/2026-09-01-overhaul/475-owner-regate.md`.
Pre-repair diagnosis:
The #474 regression reaches all nine destinations, but uninstrumented
adjacent hops take86–89s. The sampled retirement FIFO stops at the first
resident-parking poll even with no pending withdrawal/restore or global
@ -78,8 +145,9 @@ Do not increase budgets, reorder FIFO, bypass ACKs or reduce the reveal window.
**Status:** REPAIR LANDED + REVIEW-CLOSED at220bda797; lead nine-hop
convergence PASS2026-09-05, provisional until owner inspection. Overall
portal re-gate remains FAIL on separate latency #475 and capture #476;
G4 is not accepted.
portal re-gate initially failed on separate latency #475 and capture #476.
After #475 the owner accepts recall timing narrowly, but G4 remains FAIL on
#477–#481; #476 and the exact timing repeat are still owed.
Owner's repaired-exterior re-gate reaches portal destination30310005 but
never reveals. In the captured heap, center3031FFFF has completed its render