Files
Neutron/docs/checkpoint/collision-body-probe.md
T

118 lines
7.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# C4 dispatcher and ordinary-body component evidence
2026-10-26 continuation, verified2026-10-27 UTC. Original EXE SHA256
`f5281076e1a2492f2d61f87aae3f4544b6d0f535ebe33f9fbb6f78710fe1aea8`.
Originals remain unchanged. This report separates copied-code component execution
from the playable port, full original game behavior and native Windows testing.
## Recovered contracts and evidence
The [grid report](collision-grid-traversal.md) recovers47B4B0 recursion, frozen
query bounds, repeated FIFO cell visits and terminal callback ownership. The
[contact report](collision-contact-callbacks.md) recovers370/374/37C, special
material identity, separate published speed and friction. Those reports retain
addresses, file offsets, byte guards, callers, structures and REA Evidence.
Additional closed/exported REA sessions in artifacts/collision-integration/:
| Procedure | Evidence | Contract |
|---|---|---|
|47A330|ev_8be4a538fe941bcf0ba77ce64f552d4f0e17969ea87713cec5d37d39bc560735|Supported/nonzero-linear friction; published160 gates caller.|
|47C6E0|ev_ad96a93792dcf00534130fbd428fb52fa25e2cf9c2492df43f89f425b80c3f08|All-grid strict nearest support reduction, initial segment magnitude.|
|471120|ev_90314124d5ab1c88911198ef9e8d43ad7cc9e096ca075757d29c5e15cf1f86eb|Authored float8 writes live suppression scale through234.|
|470540|ev_c16f95e608194a8f9fb029430f1c6a01512d34099ebf447cf944946c79631166|Init copies authored flags/scalars through virtual setters.|
Body479D20 remains anchored by ev_5439072b32ae9f9208795ad2b07bc524e2407b46da487072fb3dfd8c10e7c4b0
in artifacts/collision-response/rea-response/. Generated source.json reports
PE-mapped offsets; the five added body hashes cover479D20/47A330/47B890/47C6E0/
469A10, alongside ten existing dispatcher/kernel bodies. Hashes and relocation
sites are checked by test_body_step_evidence.py; no arbitrary scan of executable
values is used at execution time. Short accessor recognition failures in rea-body
are retained beside successful replies, not represented as decompilation success.
## Isolated execution boundary
tools/binary/collision_dispatch_probe.c and body_step_probe.c map a generated,
hash-checked EXE copy into their own32bit process. Preferred-base mapping was
unavailable; existing guarded mapper rebases only explicit in-memory operands.
Fixtures supply synthetic grids, shape/polygon/corner arrays and virtual methods;
the body fixture supplies ordinary flags, radius60, factor1.265, friction0.8,
suppression scale0.5 and gravity(0,−800,0). No game entry point, full Jimmy
instance, source window/input/audio/script lifecycle or dynamic body pass runs.
Landing37C is an observer fixture; real ordinary Jimmy37C is a no-op.
reference_capture.py runs a separate generated Wine prefix/copy with no network
and no original-directory mount. Sources/header/identity metadata and logs are
under artifacts/collision-integration/dispatch/ and body-probe/. Initial fixture
failures are preserved: a missing Euler328 virtual was diagnosed and supplied,
and direct member42C has allocated zero storage. Those were harness omissions,
not original game defects. Automatic approval review temporarily failed due its
usage limit; after its stated reset time, a normal reviewed retry succeeded.
## Observed dispatcher results
All seven original fixtures completed with DISPATCH_COMPONENT_COMPLETE. Managed
OriginalStaticCollision regressions compare these positions and exact counts.
| Fixture | RootXYZ | Passes / primitive visits | Terminal callback |
|---|---|---|---|
|face retry|0,20,10|2 /4|wall0|
|edge retry|107.071068,100,7.07106781|2 /2|wall0|
|edges disabled|105,100,5|1 /1|none|
|zero motion|0,20,20|0 /0|none|
|forced zero/member42C|0,20,20|1 /2|none|
|corner retry|5,20,10.000001|2 /8|wall0|
|ceiling retry|0,90,0|2 /8|ceiling0|
## Observed body results
All ten copied479D20/support fixtures completed with BODY_COMPONENT_COMPLETE;
finite-output assertions pass. These are observations for the next body adapter,
not claims that a managed full-body equivalent already exists. dt is float1/60;
all unspecified vectors are zero. Initial previous support is false except jump.
| Fixture | Initial distinction | Observed result |
|---|---|---|
|floor support|RootY75.9|Y75.9000015, supported, callback sees Vy−13.333334/support=false.|
|spawn settle|RootY26|Same support root/landing observation.|
|pending jump|Supported, impulseY550, accelerationY−264|Y84.7711105, Vy532.266663, unsupported; impulse consumed.|
|fall above floor|Y100, Vy−200|Y96.4444427, Vy−213.333328, unsupported.|
|fall land|Y76, Vy−200|Y75.9000015, Vy0; callback sees old Vy−213.333328/support=false.|
|ground friction|V(100,0,50), angularY12, published speed0|Root(1.66666675,75.9000015,0.833333373); V(98.6666641,0,49.3333321), angularY11.8400002.|
|published speed|Same vectors, published speed100|Same root; V(100,0,50), angularY12, no friction.|
|stationary angular|Linear0, angularY12|AngularY12 remains; zero linear magnitude skips angular friction.|
|small motion|Vx0.125|RootX0.00208333344 then velocity suppressed to0.|
|geometry disabled|Vy200, accelerationY−264|Y75.9000015, Vy0, accelerationY800, supported, no landing callback.|
The geometry-disabled branch479DF7..479E54 sets supported, anchor and acceleration
before impulse/integration. It does not test prior grounded state. This corrects
the earlier C3 support-cancellation interpretation. With geometry enabled, the
jump fixture applies acceleration and gravity normally.
## Implementation and remaining gate
OriginalStaticCollision is currently an isolated source dispatcher/support-grid
component, invoked by tests. It preserves duplicate visits, retry state, negative
Z upper-bound quirk and terminal publication. Its explicit geometry-enable input
skips primitive calls but preserves terminal callback. TraceSupport uses strict
nearest reduction. The256-pass rejection is a defensive port boundary; original
recursion has no recovered depth limit. Double cell intermediates/modern quick
magnitude tables do not promise exact x87 boundary equivalence. Triangular route
metadata is required; general polygon fans are rejected by duplicate identity.
Prepared scenes now include signed3DMa archive IDs. Mesh keeps an explicit
identity-completeness flag; source grid construction rejects old prepared metadata.
Camera behavior is unchanged. Lab/outside contain special fence/climb/ladder IDs;
VR04 contains none. This is a scene-data fact, not proof every lab trajectory
contacts one or that all Player374 policies are implemented.
Next coherent implementation: combine the proven dispatcher with ordinary body
integration, negative-Y horizontal-first split, callback370, support/landing order,
published160 friction and suppression, comparing the ten references above. Start
with an explicit ordinary-contact subset (VR04); reject unsupported special policy
rather than silently discarding it. Then test model/root support, airborne input,
ceiling and tutorial/RETURN through the live adapter. Lab/outside require recovered
special160/164/FENCE/LADDER policies and dynamic shared nearest/last-polygon/reclip
ownership before replacement. Whole-scene registry/base transforms, camera shared
eye, original end-to-end comparison and native Windows validation remain open.