Restore original airborne steering for jumps and jetpack bursts

This commit is contained in:
UnixNight committed 2026-10-24 20:57:39 -04:00
1 parent b58138d7ba
commit 976e677019
16 files changed
+357 -54

No files matched your search

+85
View File
@@ -0,0 +1,85 @@
# Corrected airborne keyboard input
User testing exposed an error in the earlier reconstruction: Jimmy could rise
with the jet pack but could not begin moving/turning in the air. This report
supersedes the no-air-steering claim in the original movement checkpoint.
Read-only Neutron.exe addresses are VAs; text file offsets are VA-0x400000.
## Dispatch error and recovered handler
The signed mode at interface+704 (complete+7C4) selects jump table438BA4:
mode0->438B31, mode1->438B60, mode2->438B6D, mode3->438B82. Mode1 logs at
438B60, removes its printf argument at438B6A, then **falls through** to438B6D.
438B76 calls complete-object virtual128, whose Jimmy vtable4A3BDC entry is439900.
It does not return after logging. The earlier report incorrectly read that
control flow and a regression test encoded the error. Both have been corrected.
Normal jump/jetpack movement uses mode1 and the following keyboard subset of
439900. Special movement mode2 (distinct from gadget selection) shares the input
handler but has extra turn/pose/camera behavior; that full mode is not implemented.
| Input/rule | Source | Implemented arithmetic |
| --- | --- | --- |
| Left before Right |439943/439966|Left precedence; adjust turn rate by+100*dt or-100*dt|
| Release keyboard turn |439989..439A19|Move prior turn rate toward0 by100*dt, clamp crossing|
| Normal air turn limit |439D81..439DB7|Clamp rate to[-30,+30] degrees/sec|
| Up |439AE6..439B69|Add source30 speed per call, cap600|
| Coast |439B69..439BA2|If speed>600*0.909090936, subtract35*.5; otherwise retain|
| Down with positive speed |439C1D..439C78|Subtract35*.5, clamp at0|
| Down with negative speed |439C7A..439CB2|Add35 toward0, clamp crossing|
Forward acceleration precedes braking when Up/Down are both held. Turn alone
does not use ground acceleration. At normal maximum600, release coasts down
600->582.5->565->547.5->530 and retains530 until another input/ground phase.
Down brakes, rather than starting reverse air movement. These are source rules,
not a replacement walking controller enabled wholesale in the air.
## Velocity and integration
Air apply437F90 preserves vertical velocity, adds turnRate*dt to current yaw
at438011..43802B, and calculates lateral velocity at43803B..438062 as:
```
sideSpeed = turnRate * (1-friction) * speed * float(1/55)
velocityXZ = forward(yaw)*speed + right(yaw)*sideSpeed
```
Source friction is0.8. Air sideSpeed lacks the additional ground dt factor;
ground437CDx uses (turnRate*(1-friction)*speed/45+keyboardSide)*dt instead.
The port now preserves the shared turn-rate field through landing and clears it
on scene reset. Air input's destination yaw is current yaw (439E2B), so the ground
keyboard target offset does not override its direct yaw update.
AirSteering.cs translates this keyboard subset. LabSimulation calls it while
airborne, including before burst activation and after release. The
existing jetpack vertical state/effect/energy behavior remains a separate phase.
Full original input/update/rotation phase order, mouse/analog, pitch/roll/lean,
special flight mode2, collision response and camera are still incomplete. Current
integration is yaw-only at fixed60Hz with the provisional collision capsule.
## Verification
-2 Python source tests guard all four dispatch-table entries, mode1 fall-through,
vtable128 and decisive keyboard/constants/air-lateral instruction sites.
-16 movement groups pass, replacing the invalid no-air-steering fixture with
ordinary-jump response, exact keyboard arithmetic, powered takeoff-from-rest
steering/braking, left/right paths and60/120/144Hz equivalent replay.
-14 vertical jetpack groups remain passing. Input-only lab navigation still
reachesSCENE60, score150, owned jet pack and the original outside LOAD.
-The upgraded VR04 smoke starts vertically, presses Up/Left/Down during active
flight, releases the burst and lands. Headless llvmpipe renders300 frames:
powered horizontal travel403.88, one burst/landing, maximum rise418.98,
zero Vulkan validation errors. It requires actual powered horizontal travel
and nonzero turn rate, so the previous frozen-air implementation fails it.
-Window mode injects all four Up/Left/Down/Shift keys through SDL, runs300 frames
and resizes800x600. Package/runtime results are recorded in compatibility.md.
These are static and port runtime regressions; original gameplay comparison and
native Windows verification remain distinct. Original assets remain unchanged.
Final package checks: Linux self-contained GTX1070 and Windows self-contained
under isolated Wine64 both receive the full SDL input sequence, resize and finish
with identical403.88 powered travel and grounded position. Linux reports zero
validation errors; Wine validation is disabled. Logs: artifacts/package-jetpack-steering.log
and artifacts/windows-jetpack-steering-package/wine.log. Native Windows remains
unverified by the agent. All539 original hashes still match.
+9
View File
@@ -97,3 +97,12 @@ timer, energy clamp/VR immunity, depletion, explicit phase differences, absent
effect and bounded malformed input. The existing13 movement groups still pass.
These are static/data/port algorithm checks. Original gameplay/native Windows
comparison remains required before a fidelity claim.
## Airborne steering correction
User testing found frozen horizontal control during powered flight. The original
mode1 dispatcher falls through to439900; the earlier no-input interpretation was
wrong. AirSteering now supplies the separate source airborne keyboard path for
both jumps and bursts. Up accelerates, Left/Right ramp turn rate, Down brakes.
See air-steering.md for dispatch proof, exact arithmetic and new movement/GPU tests.
+6 -8
View File
@@ -44,14 +44,12 @@ support can receive the full 550 impulse with no net gravity that step,
before airborne acceleration begins. A port's immediate grounded-to-airborne
transition can differ by one tick; do not claim an exact original jump apex.
Movement dispatcher mode 1 (`0x438B60`) logs and returns without running
walking input. Ordinary arrow acceleration/turn input is therefore absent
while that air mode is active. Air apply reuses takeoff speed and rotation,
preserving vertical velocity; with the default extra turn rate zero, it has
no new keyboard steering. Its nonzero extra-turn lateral calculation uses
`turnRate*(1-friction)*speed/55`, without the ground branch's additional `dt`
on lateral magnitude, and omits the keyboard side contribution. A port that
allows normal walking input in the air should identify that as an approximation.
**Correction from user testing:** mode1 (`0x438B60`) logs and falls through
`0x438B6D` to complete virtual128=`0x439900`, the separate airborne input handler.
The earlier claim that it returned without input was wrong. Normal jumps and
jet pack flight allow Up acceleration, Down braking and Left/Right turn-rate
control. The corrected source arithmetic, regressions and remaining integration
limits are in [air-steering.md](air-steering.md). Ground input remains separate.
## Normal keyboard walking