Files

184 lines
11 KiB
Markdown
Raw Permalink 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.
# Bubble body, VR01 registration and support material
2026-11-02. Independent investigation; no modern runtime files changed. The
ordinary body can accept Bubble's radius/factor and actual VR01 static geometry,
provided the separate retained support-material callback is preserved. VR01 has
no special wall374 polygons; it does have a consequential lava floor111.
This does not reopen dynamic actors or all special-contact policies.
## Evidence and scope
EXE SHA256 `f5281076e1a2492f2d61f87aae3f4544b6d0f535ebe33f9fbb6f78710fe1aea8`.
OMT DLL SHA256 `3ec41ead011adf56387a6dbd4580e5b5a9721b5f8020c8a56420f42824354943`.
`tools/binary/bubble_body.py` PE-maps eight bounded body hashes,27 fixed sites,
ten virtual targets and the DLL texture-pointer publication, then independently
decodes VR01/VR04. Text VA minus400000 gives EXE raw offset here; DLL source
100013B5 maps raw13B5. Full facts/hashes are in
`artifacts/bubble/body/source-contract.json`; raw disassemblies sit beside it.
Relevant reused REA Evidence, with complete reports already retained:
| Source | Evidence | Retained location |
| --- | --- | --- |
|479D20 integration|`ev_5439072b32ae9f9208795ad2b07bc524e2407b46da487072fb3dfd8c10e7c4b0`|artifacts/collision-response/rea-response/|
|40E050 animated base|`ev_03a109302788b85597e253293bbcb535c4080732e41cc828bb33d01d2b2da09a`|artifacts/uncontrolled-phases/rea/|
|462520 support/material bridge|`ev_f0a2e1fd465472295b272f2fdbfb6be4651aeb8c35d90dc2ca02a495ed359edd`|same|
|OMT material read10001490|`ev_f592b625a60ec683a17627d671c47d78d722eb39d5eb407744d53a283ee2586d`|artifacts/collision-integration/contacts/rea-material-identity/03.json|
|Bubble equip/cleanup|[Bubble source report](bubble.md)|artifacts/bubble/rea-effect/|
New REA/Ghidra factor-setter4711E0 Evidence
`ev_5d2495e741932d9eb7b5a687d31b4fcc7a398d890797247ddf262677f6cf490f`
is saved/exported/closed under `artifacts/bubble/body/rea-ipc/`.
It confirms authored2C is stored and forwarded through254 to live154; the
setter changes no root.424600/44E030/4252E0 were not recognized as procedures;
their VA queries fell through to unmapped file-offset errors. These are saved
provider gaps, not successful pseudocode. Their contracts use reviewed bounded
instructions and fixed guards. The first `rea/` attempt failed because the host
sandbox denied the Unix socket; the successful local IPC retry is separate.
## Body parameters and root alignment — recovered and probed
Equip429049/429058 sets authored/live radius160 and factorfloat32(.415).
Cleanup42809C/4280AB sets60/float32(1.265). Supported wrapper42469B..4246E9
restores **live** radius160 for raw mode0,60 otherwise; it does not set factor,
reposition root or add a landing callback. It is outside the controller raw-owner
gate. The existing OriginalBodyPhysics.Step already accepts radius and factor;
the live caller must pass the current factor instead of fixed1.265.
Support47B890 uses radius×factor for final root offset. Bubble's66.4 is lower
than ordinary75.9 despite the larger collision sphere. Prevent-lowering208=true
rejects downward root correction. Consequently equip must not immediately move
the root downward, and cleanup must not preserve Bubble66.4 as the ordinary floor
offset. Inherited Jimmy landing37C→472970 is a return. Support publishes shape34C
and polygon33C through plain setters4725C0/472580; these perform no special callback.
Six additional copied-original body fixtures ran atdtfloat32(1/60), gravity−800,
friction.8, suppression.5, ordinary integration/support/world flags, no dynamic
pass and a synthetic flat triangle. Source479D20/support instructions ran inside
a copied generated32bit process; synthetic virtual methods supplied body state,
no-op contacts and a landing observer. The game entry point, real Jimmy, source
input/audio/scripts and actual VR01 geometry did not execute.
| Fixture | Original observed rootY | Original observed Vy/support |
| --- | ---: | --- |
|160/.415 at66.4|66.4000015|0/true|
|160/.415 at26|66.4000015|0/true|
|Equip160/.415 from ordinary75.9|75.6777802|−13.333334/false; no forced lowering|
|Cleanup60/1.265 from66.4|75.9000015|0/true|
|160/.415 at66.4, priorVy300|71.1777802|286.666656/false|
|160/.415 at66.4, priorVy900|81.1777802|886.666687/false|
Data, binary/source/header hashes and scope are in
`artifacts/bubble/body/original-body-results.json`; full output is
`probe/wine.log`. `--probe-source` generates the fixture source from the existing
body harness. Compile with `i686-w64-mingw32-gcc -O0 -Wall -Wextra -Itools/binary
-Iartifacts/bubble/body artifacts/bubble/body/bubble-body-probe.c -o
artifacts/bubble/body/probe.exe -lm`; generate the guarded header through
body_step_evidence.py. Run only through reference_capture.py with its copied game
directory and no-network/no-original-mount namespace. Initial6second Wine prefix
setup did not complete; the next prefix failed kernel32 loading. Both logs remain.
A separate copy of the prior working prefix completed the probe with exit0.
The constant75.9 ActorRoot/feet/render bridge remains a **modern approximation**.
Changing that bridge to radius×factor on every equip would introduce an immediate
root/render movement not justified by either setters or this probe. Preserve the
documented visual boundary and test source physics roots independently.
## Actual VR01 static filter and material coverage — closed for this archive
455EF0 constructor binds complete game table4CD740 at455F5A and registers
FourCCVR01 at455FA8. Its134→475CD0 returnsfalse, so the shared loader imposes
no extra game polygon exclusion. Shared NC44DD64, checkpoint4791C7 and
game4791D9 filters match the existing route adapter. Source shape-ID enumeration
is valid here: the archive has only contiguous shapeID0, VRRoom. All polygons
have three corners. No NC shape or checkpoint material is used.
| Archive | Shapes | Registered/all | Wall grid | Used material IDs |
| --- | --- | ---: | ---: | --- |
|VR01.omt|0 VRRoom,60 vertices|80|60|0,1,2,3,4,111|
|VR04.omt|0 Box01,336 vertices|508|420|0,2,3,4,6|
VR01 polygons48..53 alone use111 (`112lava`), all stored normalY=.991954..1.
They never register in the wall grid (requiresY<.7), so cannot dispatch370/374
through static traversal. The other eligible wall374 IDs0..4 are ordinary.
VR01 source GAM contains16 entities including one3ROC, two3PHO and a3TRO, no3SOL;
absence of soldiers does not prove all actor pairs ineligible. Dynamic actor
collision remains excluded exactly as in the bounded VR04 body implementation.
## Retained support polygon and floor111 — distinct callback
Support's no-op landing does **not** prove the floor harmless. Current support
is cleared at the next body start, but stored polygon338 is not cleared there.
462520 checks gameplay475CA0, integration210 and nonnull stored polygon338.
It reads polygon+4 material and material+80 **texture pointer**, then calls game130
with actor/material/texture/dt.44E030 requires nonnull actor and texture, resolves
material+0C→chunk+8 signed resourceID, and checks actor FourCC3JIM.
There is no218-grounded test in the110..119 branch. Preserve the last successful
support polygon until a later successful support overwrites it, even in flight.
The actual VR01 used materials all link Canv resources;111 links Canv6. This
nonnull texture gate is not the material payload's trailing3. OMT's exported
set_texture100013A0 writes the texture at+80,100013BB.
Order:424C34 calls437940;43796A calls40E050;40E0EB calls462520;46258F invokes
VR01 game130→44E030. This is before controller ownership437A2B, before applying
mode2 bounce and after the wrapper ceiling/downward queries. It remains eligible
when Jimmy is uncontrolled, subject to the common gameplay/integration gates.
For actualVR01 IDs0..4/111, the bounded source policy is:
- Enter110..119 at44E170: if complete1E02 isfalse, invoke198→42AB00 then set1E02.
42AB00 requestsSFX39 unconditionally and190 only if raw mode!=0. Bubble keeps39.
- Invoke164→42A8D0 every eligible base tick. It returns immediately if complete
1DEC isalreadytrue or raw mode==0. Otherwise set1DEC=true, sharedtimer1DE8=0,
call42A920(−5),42ADC0(−5), then complete1E0→425120. Energy retains common VR01
exemption; score still clamps after−5.425120 cancels only movementmode1.
- Leaving110..119 clears1E02 through19C→472970(no-op). Leaving does not clear1DEC.
Cleanup while still over retained111 therefore starts damage on the next base
tick without replaying entrySFX39/190 if the entry latch is stilltrue.
-111 chooses game sound selector35; IDs0..4 choose5. Selector change invokes
complete1E4→42AEC0, which only retargets a pre-existing A44 loop handle, stops it
and starts the new resource repeating. Full movement-footstep ownership is open.
This policy justifies an explicit VR01 floor111 handler, not every special contact
on LV1B/LEV1. The source ordinary wall callback remains unchanged for Bubble;
do not add generic horizontal reflection. Controller bounce/held-jump/SFX106 is
recovered separately in [bubble-motion.md](bubble-motion.md).
## Lava flash phase and rendering boundary
Late wrapper424C88 invokes4255C0. With other damage states1DED/1E03 false,
4257D6 addsdt to shared1DE8 while1DEC=true.4257E8 compares the retained x87 sum
before4257EE stores thefloat timer; the later pulse also consumes the retained
sum. Strict sum>4 (49D5E8) clears1DEC and writeswhite; at exactly4 it still flashes.
A sum just above4 can clear1DEC while the persisted timer rounds to4. Otherwise
`pulse=(sin(timer*20)+1)*.5`. It directly writes complete5C0 material+4C..58 as
RGBA(pulse,1,pulse,1). Raw mode0 does not stop a previously active flash.
42A8D0 does not call114 or another linked-material alpha setter.
1DED has earlier priority/return;1E03 precedes lava and shares the timer, possibly
addingdt before lava addsdt again. Those other damage policies remain outside
this slice. Invisible114 writes all linked materials, while this late source
write targets the one5C0 material. A port must retain explicit material-write
ordering or document the bounded renderer approximation. A fresh per-frame
Invisible RGBA snapshot cannot silently erase a retained lava write.
## Validation and recommendation
Five Python groups pass in `artifacts/bubble/body/tests.log`: original guards,
actual archive registration/texture/material coverage, Bubble entry bypass,
cleanup damage/strict4second flash including compare-before-store, and base callback gates. Six copied original
numeric cases pass as above. No modern build, port gameplay or whole original
gameplay was run by this investigator. Confidence is high for guarded source
order, actual archive counts and the isolated flatfloor body outputs; whole actor
pair eligibility, all damage-state interactions and original visual equivalence
remain open.
Minimum bounded integration: admitVR01 in the source static factory after these
registration checks; pass radius160/factor.415 and restore60/1.265 without direct
root correction; retain support polygon/material independently ofcurrent support;
run the explicit111 phase before controlled movement plus its late flash clock.
Keep dynamic/special walls parked, and preserve the75.9 render bridge explicitly.
If the111 pipeline is omitted, limit claims to raw0 Bubble body and keep ordinary
VR01/postcleanup floor behavior marked incomplete. A mode0 radius alone never
establishes full Bubble support/collision fidelity.