Trace VR04 physical registration and generated helper lifetimes

This commit is contained in:
UnixNight committed 2026-11-06 22:56:38 -05:00
1 parent 3794439d4e
commit 346d350176
17 files changed
+718 -3

No files matched your search

+77
View File
@@ -0,0 +1,77 @@
# VR04 generated helpers: bounded registration catalogue
2026-11-06. Complements [serialized registration](physical-registration.md).
This is source recovery, not a complete observed helper/body count. No gameplay
change, native actor constructor execution or package refresh is claimed.
`tools/binary/vr04_generated_bodies.py` verifies the canonical EXE hash,21 direct
calls,9 instruction sites and12 helper RTTI identities/36 method targets. Optional
`--rea` retains13 bounded instruction excerpts, PE offsets and hashes under
artifacts/physical-registration/helpers.json. Source Evidence is
`ev_0d64cc58fa8f5573fc8e61e0f2c20e36288099212bd2257d3a3121361fd6c904`.
EXE text offsets cited here are VA−400000; the guard uses actual PE mapping.
JN-Engine documentation supplied navigation leads; canonical instructions and RTTI
establish the following identities. No JN replacement movement is used.
## Positive creation/registration chains
| Owner / original VA | Helper and physical-registration evidence |
|---|---|
|Jimmy422610/422633|Loop counter20, ctor40FC50; complete+AB4..B00 stores20 C3DBaseball pointers. Table49141C+40C→410000 invokes2C at41000C→464210. The loop disables each ball's integration214; sleeping does not remove registration.|
|Player4374DF; Jimmy4238EF|C3DJetpackFire ctor421D80, table4A3160, created from the Player constructor. Its own40C→40E7B0 supplies no registration call, but Jimmy's matching-start PostLoad configures the owned fire and explicitly invokes its2C at4238EF. Owner-driven registration is essential.|
|Jimmy42243F|Owned C3DRocketShip ctor43D840, distinct from a separately created serialized3ROC instance unless the loader's reuse policy selects an existing one. Its43DB22 PostLoad invokes guarded42AB50. Do not collapse nodes by kind name.|
|Rocketship43D9BC|C3DFireStrato ctor4192E0, table49BDD4. Common40E7B0 PostLoad alone is not a registration edge; other owner/lifecycle calls remain separate.|
|Jimmy42232C|C3DBubble ctor410840; direct registration410992→464210. Its410A80 PostLoad sets up retained artwork and does not itself establish repeated registration.|
|Jimmy4225BE|C3DPointCursor ctor43BC70;43BD67→4623D0. Generic40E7B0 PostLoad supplies no own registration.|
|Jimmy422800|C3DGraplingHook (original RTTI spelling), ctor41EEB0;41EFB4→4623D0. Its generic40E7B0 likewise is not a retained re-registration proof.|
|Smoke4406B1|C3DSmokePuff ctor440980;440ACC→464210. The serialized Smoke object's own negative registration result does not exclude its helper's node.|
|Goddard41CA9C/41CB09|Two C3DCursor constructors415760, each415857→4623D0. RTTI/table497620 identifies Cursor; these are not C3DFlag helpers.|
Common registration can append an interface more than once, while the Jimmy/
Rocketship outer49E guard prevents a repeated call when set. The new native
registration cases verify that distinction; this catalogue does not assert a
natural duplicate node for every positive chain above.
## Helpers whose interface does not prove body membership
- Jimmy42250C creates C3DShadow43F640, table4B37B8. Yokian44A88F creates the same
type conditionally on the source shadow flag. Their retained-canvas PostLoad
43F810→4354C0 is not itself a2C call. Terrain projection is a separate consumer.
- Jimmy42255B creates **C3DTargetCursor**4453B0, table4B9F48. It is distinct from
C3DMovingTarget/table4A8A10 and the target consumers used in VR07. Shared FourCC
3TAR or misleading class-registration strings are insufficient type evidence.
Its445580 retained-canvas setup does not establish body registration.
- Yokian44A826 creates C3DYokianShield44B510, table4C0E24. Its44B6C0 PostLoad calls
464810 canvas setup; exposing2C→464210 alone proves no physical-list membership.
The catalogue is bounded: additional Jimmy allocations (including ray/pod paths),
conditional helpers and owner callbacks still need their own lifetime inventory.
The12 listed RTTI identities are not an assertion that only12 helper types exist.
## Retained loads and late companion construction
Ordinary scene teardown clears the physical list; it also clears surviving
interfaces'49E flag. A retained registry identity is not a retained physical node.
Baseballs' explicit PostLoad and Jimmy-owned fire invocation give positive re-entry
edges. Constructor-only helper registration cannot silently be treated as a
PostLoad edge; gadget activation, later owner calls, reuse/removal and shutdown
must be followed before assigning retained membership.
Jimmy PostLoad423C98 constructs Goddard only on its observed pointer-null path.
The Jeep path is different: EDI is zeroed at4236FA and stored into game+970 at
423792, before the later null test423CEE and constructor4211A0 at423D1A. Therefore
the later null test alone is not evidence that this pointer is retained. Source
421552 invokes Jeep2C→421570, whose49E guard enters465070→4623D0. Jimmy423D75
then calls the wheel-construction hook; existing Scooter documentation covers its
four wheel objects. Old Jeep teardown/deletion and complete retained ordering
remain open; no leak or new carry/reset policy is inferred.
## Implementation consequence
The live port reconstructs selected actors and bounded body records per scene.
It does not yet reproduce this complete helper/physical-list lifecycle. The pair
component must receive source physical order with real actor callbacks, not a
filtered list of visible GAM actors or a dictionary containing one actor per kind.
No helper is added to live collision merely because a vtable exposes InitPhysics.
Resolve remaining constructor-only re-entry, deletion and activation edges before
changing that boundary. All source/probe work remains local and originals unchanged.