Files
Neutron/docs/gameplay/rocketship-live.md
T

6.3 KiB
Raw Blame History

Live VR02 Rocketship checkpoint

2026-11-03. Continues312efcc with a bounded playable aircraft in the authored VR02 scene. Original files and supplied friend research remain unchanged. No friend gameplay code was imported. Baseline69d0187 and parked collision 35a2a66/0272f7b remain available for comparison.

Controls

F1 → Player → Give/Select Rocketship grants its tile. Outside VR02 this retains the selection for Practice without enabling an invented player-flight mode. Open Tab/Space, choose the Rocketship tile and Practice to enter VR02. Equip there using the tile or F1 action. Up/right mouse accelerates and climbs, Down brakes/descends, Left/Right banks. Enter/T turns180 degrees; R barrel rolls. Tab/Space unequips before opening the gadget panel. R resets while unmounted.

Source and implementation coverage

Source addresses, structures, caller chains, file offsets, REA Evidence IDs and component-probe provenance are in body, motion/camera, lifecycle and the earlier component report. EXE text file offsets are VA−400000. Original executable/DLL hashes are guarded by the analysis tools.

Original contract Current implementation and evidence Remaining boundary
Jimmy-owned reusable3ROC, ID reuse and mount/cleanup Rocketship binds the sole authoredVR02 actor; PlayerSceneBinding transfers ownership, seeds root/Euler/shared eye, preserves remount motion and stops engine/fire on release General retained helper registry across levels
Body before input/normal, fresh/retained registration order Explicit StepBody, LabSimulation afterPhysics hook, input-before/after normal according to InputAfterPlayerUpdate Full original traversal and original frame cadence
Radius50/factor.6/friction.8/prevent-lowering; ceiling370 and wall374 Rocketship body profile with native support references and ordinary material effects Other-level materials, special damage, complete pair scheduling
Jimmy1E4 dynamic inhibit, independent static body Jimmy static physics continues before ship root/Euler synchronization General dynamic push/recording implementation
Scalar/bank, vertical command, Euler/facing/slip, turn/barrel RocketFlight/RocketOrientation/RocketMotion compare against copied-original numeric fixtures General x87 bit identity and all modal globals
LOOK→eye clip, shared OLD eye, detail gain and quantized angles OriginalCameraRay plus source camera math; both detail branches checked in components Whole-game shared camera ownership, detail initialization and renderer parity
Strato/HIDRIVE/HIROCK/FireStrato and engine195/196, hit197 Exact extracted morphs/textures; source pivots/full Euler, Goddard offset, additive flame; unchanged engine mode does not restart Scripted effects, EC0/ED0, RNG and20 linked effects
Controlled-owner pickup vs named-Jimmy LOAD Ship radius50 used for3PIC; real passenger radius60 used for LOAD Port sphere discovery remains an adapter; no full pair-order claim
Control loss and menu/reset/noclip Named-Jimmy MCA release, FALL cleanup, shared eye handoff, Tab/Space, F1 force-control, reset and F3 cleanup Generic post-vehicle Jimmy Euler/render bridge and complete transition persistence

Corrections replace earlier symptom-level assumptions:1E4 does not disable integration, input is not unconditionally after normal, camera trace starts at LOOK rather than ROOT, and turn/barrel controls are not boosts. No nearest-ship search, direct vertical-velocity substitute or standing-foot art correction is used for this vehicle.

Verification

96 isolated copied-original observations:14 keyboard,14 vertical,31 motion/facing/camera,23 callbacks,6 support and8 impact suffix cases. These run copied EXE/DLL components with synthetic accessors in separate Wine32 prefixes; they do not run original gameplay. Committed fixtures and source guards allow repeatable projection checks.14 managed flight groups and12 final Rocketship integration groups pass. The latter cover actualVR02, fresh/retained input, mount/remount/audio, source support, ceiling/wall, pickup/LOAD identity, RETURN, resources, force-control and named-Jimmy cleanup.

Full scripts/test.sh passed268 Python regressions+2 HUD checks, all managed suites,33 main GPU completions and17 material checks, with zero Vulkan validation errors and539 original files unchanged. Its Rocketship integration run had10 groups; the final two force-control/MCA groups and tiny related fixes were checked afterward by the12-group focused run. The initial selected-project compilation failure was corrected by accepting a DirectorActor contact descriptor instead of depending on Rocketship; its failed log is preserved separately.

Headless and native Linux GTX1070/private Xvfb1920×1080 replays pass all10 phases: mount, flight, bank, turn, roll start/barrel, release, remount and noclip cleanup. Native replay receives real injected SDL Up/Left/Enter/R/Tab/F3 events (mask63), stops engine audio and reports zero enabled Vulkan validation errors.295 extra ordinary ticks reuse received input through binding/interactions/director without teleporting or seeding motion/timers; this is accelerated port verification. Energy stays20. Captures show Jimmy/Goddard/fire attached during maneuvers.

Logs and readbacks: artifacts/rocketship-live/{integration.log,headless.log, native-ipc.log,phases.png}; initial failures are retained separately. The initial native sandbox could not access local X11 sockets; a locally approved IPC run succeeded. No network display, uploads or original entrypoint execution occurred.

Release and next work

Clean-source Linux/Windows package provenance and standalone replay are recorded after local packaging below. Native Windows execution remains unverified for this milestone; cross-publishing does not establish it.

Next evidence gates are non-VR02 reuse/level lifetime, special hazard/mission consumers, shared-camera and general Jimmy Euler presentation after cleanup, and full original actor-pair scheduling. Grappler and Scooter retain their separate recovered contracts and are not enabled through approximate mechanics. Manual original-versus-port tutorial completion and native Windows testing are still required for broader fidelity claims.