Files
Neutron/docs/checkpoint/body-root-registration.md
T

47 lines
2.9 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.
# Retained identity and physical re-registration
2026-10-26. Static evidence, not whole-loader execution. Original EXE SHA256 is
f5281076e1a2492f2d61f87aae3f4544b6d0f535ebe33f9fbb6f78710fe1aea8.
Text offsets are VA−400000; body_root_registration.py guards14 instruction
sites and four Jimmy interface targets from PE-mapped bytes.
Ordinary teardown479000 clears physical records/body list695D3C, while game
object identity can survive in registry50999C.46E131 explicitly clears surviving
interfaces'49E registration flag. Jimmy PostLoad4238B4 invokes interface2C→42AB50:
false49E jumps to4623D0 InitPhysics. Identity retention is not physical-list retention.
4623D0 invokes base458910 (470A00 allocation/49E=true), copies current render XYZ
complete44/48/4C through16C→471630, copies angular-unit Euler through174→4716D0,
then calls479A40.479A65 invokes interface150(0,0,0);479A6F invokes Init28 AGAIN,
resolving to Jimmy437890. Only then does it append a12-byte body-list node with
the interface payload and increment695D40. Later PostLoad STRT placement and
final control preparation have their own order; registration's Init is not a
blanket post-placement reset. Existing retained scalar conclusions remain bounded
by the closed437890/generic Init chain, not by an assumption that Init runs once.
| REA routine | Evidence ID |
|---|---|
|4623D0|ev_d60cfc7d2ff8266e19176052e1466ba98f09e7b10b92db828566fbc28d36d281|
|458910|ev_a7ef1cecf9385efe4f91ad8ec48ac37ba24831a1b797f24c3039a912f0b61526|
|479000|ev_bae5aeaa4f8ebad1bba6974e9d33ba801959500e41eadc99be5e6b8631feecc1|
|479A40|ev_40105808ae5a1e83bd8221b627e9aeca89b0f399a68dba068ed01e5b11857438|
Complete replies/exports/closed snapshots: artifacts/body-root-registration/.
Some additional requested leaf/derived entries lacked analyzed Ghidra procedures;
their error replies remain alongside successful Evidence. Instruction bytes and
resolved vtables support the callback chain without claiming complete pseudocode.
Previously recovered dimensions remain: ordinary radius60/support factor1.265,
physics position interface214..220, direct physics-to-render XYZ copy4624B0, shape
min/max bound records1C4/1D4. No recovered capsule height follows from mesh bounds.
The standing animation offsets observed in the older copied-DLL probe were zero;
there is still no source evidence for the port's sole-based model translation.
The port reconstructs body state per scene and carries only mode/hold/fire in
its bounded route container. That agrees with the reset boundary at a coarse
level, but does not reproduce source allocation/physical-list order/new helper
traversal or the complete body338 record. REA's prior40E050/462520 Evidence also
shows base transform work before ownership; port destination-yaw smoothing is
not proven equivalent. These remain C3/C4 implementation gates. No extra state
carry, scale correction or live body-shape replacement is justified by this report.