History

Erik 754d59d949 fix(render): shadow-gated-off receiver frames light from the authored sun again (Campaign VM VM6 review 5) Round 4 (`eec95535`) fixed wind but introduced a new lighting bug: the receiver VERTEX shaders source the sun direction from the shadow block, not only the shadow visibility term. mesh_atmospheric.vert's accumulateLights read uShadowLightDirectionAndSource unconditionally for every directional light; terrain_atmospheric.vert did the same for its single sun term. Round 4's PublishDisabledReceiverBinding writes direction (0,0,1) into that block on every shadow-gated-off frame (user sun-shadow-strength 0 in daylight, indoor/portal cover, night), so every such frame was lighting outdoor terrain and objects from straight overhead instead of the authored sun. Publishing the environment's real direction would not have restored parity either -- the celestial shadow source direction (sun/moon disc) is not the authored light direction. F1 (BLOCKER): fixed in the shaders themselves, exact parity with the plain pipeline. Both receiver verts now branch on the same flag bit acdreamDirectionalShadowVisibility already reads ((uShadowTextureAndFlags.w & 1u) == 0u) and, when clear, use the EXACT plain-pipeline expression instead of the shadow block's direction: -uLights[i].dirAndRange.xyz in mesh_atmospheric.vert (matching mesh_modern.vert, hoisted out of the light loop as a uniform branch); -uLights[0].dirAndRange.xyz in terrain_atmospheric.vert (matching terrain_modern.vert's sunDir/-sunDir form). The (0,0,1) word in the disabled block stays as the documented normalize()-cannot-NaN guard; its comment now says so explicitly since it is no longer read as a light direction when the flag is clear. F2: RenderPrepared's cascadeCount == 0 return is a third bufferless- disabled path reachable from a frame that already passed Render's own two gates (the cascade fitter can still find zero usable cascades) -- publishes the same disabled binding now, via the same PublishDisabledReceiverBinding helper (re-signatured to take a bare AtmosphericFrameBufferBinding so all three call sites -- Render's two early-outs plus this one -- share it). F3: removed a stray duplicated " -- Closeout and merge" fragment under the plan's VM7 heading. F4: corrected the false "the flag bit makes it numerically the plain lighting sum" claim in the plan's round-4 paragraph and in WbDrawDispatcher.DirectionalShadowReceivers.cs -- the flag bit alone only fixed the shadow VISIBILITY term (already correct before round 4); it took both that AND round 5's light-DIRECTION fallback to actually match the plain pipeline. T1: extracted Render's gate prologue (environment evaluate -> two early-outs -> PublishDisabledReceiverBinding) into internal EvaluateGateAndPublishDisabledBinding(frame, in input, out environment, out environmentGateTicks), behaviour-preserving, called by Render before it touches world/terrain -- the ArgumentNullException.ThrowIfNull(world)/ ThrowIfNull(terrain) calls keep their exact position relative to the gate. No test in this suite constructs a real WbDrawDispatcher + TerrainModernRenderer pair (still true), so this extraction is what makes the gate itself testable; two new tests drive it directly with PlayerInsideCell: true and with ResidentMaximumReachMeters <= CameraNearMeters, asserting TryGetCurrentFrameBinding true / IsValidFor false for both. T2: proves the actual composition WbDrawDispatcher.PipelinesFor and TerrainModernRenderer both use -- TryGetCurrentFrameBinding feeding ShouldSelectReceiverPipeline -- selects the receiver pipeline for the atmospheric world pass once a disabled binding is published, and still refuses a non-atmospheric pass name. T3: shader-source guard (same style as AtmosphericPostProcessGraphTests' existing shader-text tests) pinning that both receiver verts contain the flag-gated fallback and reference the same uLights expression the plain verts use, so a future edit that drops the fallback fails this test instead of only showing up in a pixel capture. T4: the (0,0,1) test's doc comment and an inline assertion comment now say the value is a NaN guard, not a light direction. Regenerated SPIR-V: mesh_atmospheric.vert and terrain_atmospheric.vert recompiled to different bytes this time (a real code change, not a comment); manifest updated to match. Verify: Release build 0 warnings/0 errors. App hermetic-lane filter 6,054/0 failed. Core.Tests 4,695/0 failed. RenderPackValidator 30/30. Full hermetic-filtered solution: 15,282/0 failed across 15 projects. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-08-23 03:58:41 +02:00
..
architecture	fix(render): correct foliage-wind classification, receiver/caster desync, and frame binding (Campaign VM VM6 review)	2026-08-23 01:54:36 +02:00
audit	docs: update audit — Sprint 1 items verified (sequence counters + scenery LCG)	2026-04-13 13:51:39 +02:00
plans	fix(render): shadow-gated-off receiver frames light from the authored sun again (Campaign VM VM6 review 5)	2026-08-23 03:58:41 +02:00
reference	docs(reference): preserve local ACE command catalog	2026-07-27 00:03:58 +02:00
render-packs	fix(render): correct foliage-wind classification, receiver/caster desync, and frame binding (Campaign VM VM6 review)	2026-08-23 01:54:36 +02:00
reports	docs: the overnight consolidation report, open questions first	2026-07-29 03:54:43 +02:00
research	docs(vm3): closeout - owner gate brief with the measured curve table; #422 filed; tests pin the shipped defaults	2026-08-22 23:53:26 +02:00
reviews	docs: close r3 test cleanup	2026-08-18 17:02:15 +02:00
superpowers	feat(launcher): complete Campaign LA11 pre-gate support	2026-08-15 00:02:04 +02:00
bugs.md	docs: reconcile project status and navigation	2026-07-20 13:00:41 +02:00
ci-and-releases.md	docs: note that docs-only pushes skip the pipeline	2026-08-19 16:15:04 +02:00
ISSUES.md	docs(issues): #423 - ray/shadow/volumetric day-group policy keys on the raw index, not WeatherKind	2026-08-23 01:08:32 +02:00
README.md	docs: point the documentation map at the Timing lane	2026-08-19 15:37:44 +02:00
release-gate.md	feat(render): implement Campaign AR and terrain fidelity	2026-08-22 13:13:29 +02:00

README.md

acdream documentation map

This page is the entry point for project documentation. It distinguishes current sources of truth from implementation history so an old plan or issue banner cannot silently override the current program state.

Current snapshot — 2026-07-27

Milestone state: M3, “Cast a spell,” landed 2026-07-21. M4, “Live in the world,” is active.
M4 gameplay program: resume the pre-M4 world-interaction completion program. Favorite-spell overflow, status Use/Assess, and the complete assessment surface are user-accepted. Equipped-child picking and vendor browse/transactions remain Slices 4–6.
Structural/runtime state: all eight GameWindow decomposition slices, Modern Runtime Slices A–J, and the connected visual/lifecycle gates are complete. GameWindow is a 1,622-line composition/callback shell. AcDream.Runtime.GameRuntime owns canonical session, entity/object, gameplay, movement, physics, projectile, environment, and portal state; graphical and no-window hosts borrow the same owner graph.
Headless state: Slice K is complete. AcDream.Headless is a presentation-free Windows/Linux host with deterministic commands/events, shared immutable content, multi-session isolation, reconnect, resource telemetry, and 1/5/10/30-session gates. The final two-account native-Linux soak completed ten minutes, logged out through ACE, and converged every ownership ledger.
Linux graphical state: Slice L0 and the L1 implementation checkpoint are complete at 66f114b2 and 11501d52. Native Windows passes the active modern-GL/audio/window smoke. WSLg X11/Wayland correctly reject their missing GL_ARB_bindless_texture. Physical-Linux validation and L2–L6 are explicitly deferred; resume at the supported AMD/NVIDIA L1 gate.
Completed gameplay gates: R6 locomotion/collision/projectile/teleport/ radar, two-client portal-out/materialization, indoor prepared collision, loot ordering, local/remote ground drops, and selection-marker lifetime.
Separate visual verification: issue #225, the shared-alpha lifestone/particle result; its connected resource-lifetime and performance routes pass.
Carried behaviour debt: issue #153 (far teleport onto an unstreamed edge), #116 (narrowed slide response), #235 (capped/RDP jump cadence), and the active temporary-stopgap rows in the divergence register.
Divergence audit: 189 active rows — IA 18, AD 38, AP 91, TS 38, and UN 4 — plus retained struck/retired historical rows such as TS-37.
Latest automated baseline: the Release build succeeds with the 17 test-project warnings tracked by issue #228; 8,826 tests pass and five are intentionally skipped. App passes 3,763 / 3 skips. The L1 Windows supported smoke and WSLg X11/Wayland negative-capability reports all end with zero window/GL/input/audio ownership.

Sources of truth

Read these in this order when deciding what to do next:

plans/2026-05-12-milestones.md — the active playable outcome, freeze boundaries, and visual gates.
plans/2026-04-11-roadmap.md — strategic phase ledger: shipped, active, deferred, and future work.
ISSUES.md — tactical defects and small follow-ups. The status inside an issue is authoritative; physical order is not.
architecture/retail-divergence-register.md — every known place runtime behavior can differ from retail.
architecture/acdream-architecture.md and architecture/code-structure.md — ownership, dependency, update-thread, and extraction rules.
architecture/worldbuilder-inventory.md — rendering/DAT code already owned in-tree versus mechanisms still ours to port.

If these disagree, milestones control the current outcome, the roadmap controls work ordering, the issue status controls the individual defect, and the architecture documents control implementation shape. Reconcile the stale document in the same change; do not leave both claims standing.

Research and implementation records

research/named-retail/ is the primary retail oracle: named pseudo-C, headers, symbols, and types from the Sept 2013 build.
research/decompiled/ is the older Ghidra fallback.
research/ contains focused pseudocode, traces, fixtures, and gate reports. A dated research note records evidence; it does not become a new roadmap.
superpowers/specs/ and superpowers/plans/ are per-slice design and execution records. Completed plans remain historical.
ci-and-releases.md is the SSOT for the Gitea CI pipeline, the self-hosted runners, and how alpha releases are published. Load-sensitive tests live in Lane=Timing; see release-gate.md before adding to it.
audit/ contains completion and conformance audits.
reference/ace-commands.md preserves the local ACE server's complete in-game command catalog and points to the authoritative per-command help surface.

Durable memory

../claude-memory/MEMORY.md indexes the live subsystem memories and the render/physics digests. Read a domain digest before changing that subsystem, especially its DO-NOT-RETRY table.
../memory/ contains stable engineering references such as the modern rendering pipeline, two-tier streaming, and toolchain notes.

Memory accelerates recall; it does not outrank the canonical documents above. When current truth changes, update the relevant canonical document and distill only the durable lesson into memory.

Historical and deprecated documents

bugs.md is the April 2026 bug snapshot. It is preserved for archaeology and is not an active ledger.
Dated plans and specs describe the decision at that time. Their completion wording is historical unless the current milestone/roadmap explicitly links the item as active.
Old R1→R8 architecture sequencing is superseded. Current execution comes from the milestones and strategic roadmap.

Documentation maintenance rules

Update milestone, roadmap, issue, divergence, architecture, and memory claims in the same commit when a shipped change affects them.
Keep one issue ID per defect. Narrow an issue in place; do not reuse another issue's number as a shorthand.
Mark automated, connected, and visual gates separately. An automated pass is not a visual acceptance, and an RDP throughput sample is not a local-display visual comparison.
Preserve research history, but remove stale “current/next” claims from living documents once the state advances.

README.md Unescape Escape