Files
Neutron/docs/gameplay/rocketship.md
T

172 lines
10 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.
# Rocketship ownership and bounded flight components
2026-11-03. Original static recovery, guarded bytes and two isolated original
component probes. Friend research supplied useful class/function names; its
prototype vehicle mechanics were not imported. No live vehicle implementation
or original whole-game/native Windows verification is claimed by this report.
Primary owns any modern integration and its separate validation.
## Evidence and identity
EXE SHA256 `f5281076e1a2492f2d61f87aae3f4544b6d0f535ebe33f9fbb6f78710fe1aea8`.
`tools/binary/rocketship.py` guards ten source spans, six virtual targets and eight
constants, with PE-mapped file offsets in
`artifacts/rocket-contract/source-contract.json`. These .text VAs map to raw
offset VA−400000. Full disassembly windows are retained beside the report.
No friend OMT2.dll address is assumed applicable to our different DLL build.
| Source | REA Evidence | Retained path |
|---|---|---|
|43D840 constructor|`ev_0f31a079ff84847fd27d3e41de320d6bedddcbf3917b5f3e2b345773809a0b86`|rocket-contract/rea-core/01.json|
|43DD10 visual/body init|`ev_d7bf671456c93939ac04ab612e10181e729e078de4bfc06b22f4b5302d71da00`|rocket-contract/rea-core/00.json|
|41A140 apply|`ev_ba8607f59d6ebc468cd956e6b1c8d295eecb21889055130da4706e6cbc8e6ba2`|rocket-contract/rea-flight-ipc/00.json|
|41A6C0 input/camera|`ev_ef4490ca220408f61e74f4d122b472f9055475ec4b51e2446620a54ffd1c7b2c`|rocket-contract/rea-flight-ipc/01.json|
|43E7E0 controlled callback|`ev_20502f86a5c3c7bee2ea47608f89d578286785d1ba540b5fa7f7e56ed90505a0`|rocket-contract/rea-flight-ipc/04.json|
|4192E0 fire constructor|`ev_4f74f2325cf84e07d75696f1903bfff3800a02f9b6b706431a5b90b66a83c914`|rocket-contract/rea-flight-ipc/05.json|
Paths in that table are below `artifacts/`. Complete replies, bundles and closed
snapshots are retained. Initial `rea-flight/` failed at the known local Unix
socket sandbox boundary; one IPC-authorized retry succeeded.43DB10/43DF70 still
are not recognized as procedures in that profile; their saved errors are not
pseudocode evidence. Their bounded source instructions are guarded/reviewed.
419550 was queried as a possible effect initializer but is Flag construction;
it is not used to establish Rocketship behavior. No configuration was changed.
## State ownership, selection and cleanup
Jimmy's complete object owns a separate Rocketship allocation at+AB0, initialized
through constructor43D840; complete vtable4B2A4C, game-interface
vtable4B25AC at complete+C0. The ship's complete+740/interface+680 is a pointer to
the **complete Jimmy rider**, resolving the friend's unnamed linked-actor field.
Twenty other linked slots retain a separate unresolved effect/child role.
Item1 branch42944D..429686 uses this owned pointer; there is no nearest placed
3ROC search. It activates the ship, copies Jimmy root/Euler via game310/328 into
ship318/330, transfers game118 control to ship+C0 at4295A5, stores rider+740 at
4295B4, inhibits Jimmy dynamic push/recording through1E4 (his static physics still
runs), hides/disables relevant
companion flags, selects Jimmy DRIVE and writes raw gadget1 at42967F. Null owned
pointer skips this equip body. Availability/HUD commands remain separate.
Raw1 cleanup428512..42871D disables/hides ship flags, restores Jimmy game118
ownership at4285BA, restores companion policy, clears ship+740 at4286AE, clears
Jimmy acceleration/velocity, selects the normal animation/movement state, closes
HUD mode and writes raw−1. The original raw cleanup belongs to ownership change,
not just a rendered model toggle. Retained helper life and unmount-root timing
need the ordinary update/loader context before live integration.
43DD10 game110→471240 initializes authored34 and live15C **radius50**, not a visual
scale50.43D840 sets factor float32(.6); inherited419B70 sets friction float32(.8).
Thus ordinary radius×factor support clearance is30, distinct from Jimmy75.9.
Shape transforms/render scale are separate. This corrects the friend report's
"visual scalar" label. No wheel child construction was observed.
## Input/apply ordering and exact bounded arithmetic
Rocket registry update43DF70 calls inherited41A140 before its passenger/effect
tail. Controlled callback43E7E0 gates on407060 false and475CA0 true, then invokes
41A6C0, optionally updates a fire-held timer and calls rider complete1AC with dt.
**Apply consumes retained input state; input does not integrate the body.**
Game475A70 dispatches controlled-input3CC separately; fresh/retained registry
order determines whether it precedes ship update. The live continuation and
corrected flag/order contracts are in [rocketship-live.md](rocketship-live.md).
Offsets below are relative to the game interface (game pointer=complete+C0;
addC0 to these offsets for complete-object fields): speed608, bank614,
previous bank618, cap604, max height620,
up/down638/639, prior keyboard-bank flag63A, vertical command65C, mouse pitch66C.
The shared flying properties include acceleration5FC400, deceleration6001,
cap6041400, height620, rates624650/628−650 and velocity cap62C650. Inherited
constructor defaults are distinct from GAM reapplication and level-specific259
overrides;43DCE1 writes VR02 max height3900.
Keyboard/zero-mouse41A6C0 order:
1. Left bank +=160dt; else Right -=160dt. After keyboard release a retained
keyboard-origin bank approaches0 at130dt. Mouse-origin bank has no such return.
2. Up adds AccelRate **per callback** if below cap, then clamps cap. Without Up,
speed>cap×float32(.90909094) loses DecelRate×.5 per callback.
3. Supported state independently subtracts500dt, clamped0, even with Up held.
4. Down subtracts DecelRate×dt if supported or DecelRate×.1 in air from positive
speed; negative speed adds DecelRate toward0. Up+Down still performs this
braking, then Up clears the published Down flag. Bank clamps to±45.
Source Up/Down keys are50985E/509860, Left/Right50985D/50985F. Analog thresholds
are strictly>.5/<−.5. Right mouse509834 and accumulated mouse pitch>15 also give
Up;50993A or pitch<−15 give Down. Mouse Y accumulates×dt and moves toward the
±10 band by20dt outside it. Nonzero mouse X supplies bank delta×dt instead of
keyboard steering. Boost/barrel-roll globals and complete camera tail remain
outside the primary keyboard component; do not expose ordinary keyboard scope
as complete input support.
41A470..41A6A8 vertical publication is independently recoverable:
- speed<100 preserves prior65C and skips the height decision.
- At speed>=100, rootY>=MaxHeight clamps root only and sets command0, or DownRate
if prior Down. Below ceiling, prior Up/Down selects their respective command.
- Neutral uses−160 for Vy>0,+160 otherwise; strict−60<Vy<60 snaps Vy and command0.
- Body accelerationY becomes command−global gravity, preserving X/Z acceleration.
Existing Vy is then independently clamped±MaxVertVelocity, preserving X/Z.
UpRate/DownRate here are **acceleration commands**, despite the friend's velocity
target naming. Above-ceiling positive Vy is not immediately zeroed. No source
position integration occurs in this component beyond the direct ceiling clamp.
## Actual VR02 static scene gate
456270 constructor binds complete game table4CDD30 at4562DA and registers VR02
at456328.4563D0 is Init, not construction. Table4CDD30+134→475CD0 returnsfalse,
so shared4791C7/4791D9/NC registration has no additional VR02 game exclusion.
Resource-side material/shape inventory is in rocketship-assets.md; it does not
by itself establish flying body callbacks or dynamic actor eligibility.
## Isolated original numeric verification
Two generated32bit probes map copied EXE sections and rebase explicit guarded
global operands. The input probe executes original41A6C0 through41AC0E, replacing
mouse polling with fixed inputs, supplying synthetic support/Euler/audio virtuals,
and skipping the camera tail. The vertical probe uses a small frame thunk into
unchanged41A470..41A6A8 and synthetic body getters/setters; horizontal/animated
prefixes and integration do not execute. Neither calls the game entrypoint.
Both ran through `tools/recon/reference_capture.py` in separate generated Wine32
prefixes, with no network or original-directory mount, exiting0.
| Selected case | Original observation |
|---|---|
|Up airborne dt1/60 and dt.1|speed400 for both|
|Up supported dt1/60|391.666656|
|Up+Down airborne / supported|399.899994 /391.649994; Up true, Down false|
|Coast1400 /1200|1399.5 /1200|
|Down1000 airborne /supported|999.900024 /991.650024|
|Left+Right dt.1|bank16, Left wins|
|Prior keyboard10 /mouse10 neutral|bank0 /10|
|speed99,root5000,Vy900,command123|root5000,Vy650,command123,body acceleration923|
|Ceiling Up,root5000,Vy300|root3900,Vy300,command0,body acceleration800|
|Neutral Vy±60|retained velocity, command∓160|
|Neutral Vy±59.99|velocity0,command0,body acceleration800|
|Up /Down with gravity−800|body acceleration1450 /150|
All14 input and14 vertical cases, exact float32 inputs, tuning, observed outputs,
EXE/body/generator/probe/log hashes are in `original-input-results.json` and
`original-vertical-results.json` below `artifacts/rocket-contract/`. All vertical
cases preserve synthetic XZ velocity11/22 and acceleration33/44. Logs, compiled
probes and generated C remain there. Exporter flags `--probe-source`,
`--vertical-probe-source`, `--probe-log/--probe-executable` and vertical equivalents
reproduce the source and ingest complete logs; incomplete/duplicate cases reject.
These are isolated original arithmetic references, not original gameplay traces.
Three Python source/identity/incomplete-capture regression groups pass; both
generated probes compile with i686-w64-mingw32-gcc `-O0 -Wall -Wextra`.
## Safe implementation boundary and next gates
The primary implementation and its28 numeric comparisons are recorded in
[the component checkpoint](rocketship-component.md). Do not enable a live
Rocketship controller until:
normal horizontal Euler/slip/roll/facing and actual camera record updates are
closed; aircraft-specific body370/374/378 callbacks are composed; registry/control
handoff and retained-helper life are integrated; owned-versus-placed3ROC property
and reset timing are proven; passenger/Goddard/fire attachment and effect/audio
ownership are implemented. Collision/impact/mission sequences remain separate
gates. Do not turn this recovery into tuned nearest-rocket boarding or assume
ordinary Jimmy collision/camera matches the vehicle.