Recover and verify static collision traversal and body contracts

This commit is contained in:
UnixNight committed 2026-10-26 21:45:57 -04:00
1 parent 7c0d1a4b0c
commit df0263b26e
34 files changed
+1962 -17

No files matched your search

+47
View File
@@ -1,5 +1,52 @@
# Progress — 2026-10-26
## C4 static dispatcher, contacts and ordinary-body probe
Independent REA investigations and primary integration recover47B4B0's reachable
retry, source-order cell/FIFO duplicates, mutable nearest/last-polygon state and
terminal normal callback. OriginalStaticCollision implements this bounded grid
dispatcher and strict nearest support query as an isolated component. It remains
outside the playable body path. Seven copied-original dispatcher fixtures match
managed positions, pass/visit counts and callback polygon observations. Review
corrected initial nearest-distance gating and geometry-disabled publication with
retained callbacks. All investigator file ownership returned to primary.
Recovered370/374/37C, landing-before-velocity-clear, published160 versus controller608
and friction/suppression. The Player material discriminator is linked3DMa archive
ID, proven through OMT2.dll loader/database/chunk layout, not payload flags or a
render index. Scene preparation and Mesh now preserve signed IDs/completeness;
old metadata is rejected by the new source dispatcher. Actual LV1B/LEV1 contain
special climb/fence/ladder IDs; VR04 contains none. Special policies remain open.
Ten copied479D20/support fixtures completed in an isolated Wine32 harness with
synthetic ordinary-body virtual contracts. Results cover support/settling,
pending jump, falling/landing, friction versus published speed, stationary angular
motion, suppression and geometry disabled. They are numeric references for the
next adapter, not verification of a managed whole-body implementation. Corrected
C3's earlier support-hit inference:479DF7..479E54 cancels gravity/vertical velocity
when global geometry4F69E5 is disabled, not on ordinary grounded jumps. Prior
harness omissions/logs and temporary approval-review usage failure are retained;
after the stated reset, normal approval review succeeded and the probe completed.
Full scripts/test.sh passes:122 Python checks plus2 HUD checks, all managed groups,
27 GPU completions with zero enabled Vulkan validation errors, SDL dummy lifecycle
and539 unchanged originals. Eleven focused dispatcher groups pass, including actual
route material coverage, legacy metadata rejection, retained context and support
ties. Logs: artifacts/collision-integration/integration.log, dispatcher-tests.log,
dispatch/wine.log and body-probe/wine.log. No new native Windows or whole-original
game comparison is claimed. Existing baseline/release packages remain untouched.
Both self-contained RID builds succeed into separate artifacts/collision-integration/
build directories. Restore emitted NU1900 for unavailable vulnerability metadata;
compilation/publish succeeded. These are build artifacts, not a new package release
or native Windows runtime verification. Logs: build-linux.log/build-windows.log.
Reports: checkpoint/collision-grid-traversal.md, collision-contact-callbacks.md,
collision-body-probe.md and collision-integration-review.md. Next: ordinary body
composition against the ten references, then an explicit VR04 live subset with
root/input/ceiling/RETURN checks. Lab/outside replacement additionally requires
special callbacks and dynamic shared-context/reclip order. Shared camera eye,
audio clock/banks and remaining plan chunks follow their existing gates.
## C4 sphere response and ceiling continuation
REA investigated47BD80,479D20,47BBB0,47B4B0 and projection helpers on a generated