Restore original airborne steering for jumps and jetpack bursts
This commit is contained in:
1 parent
b58138d7ba
commit
976e677019
16 files changed
+357
-54
No files matched your search
@@ -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
|
||||
|
||||
|
||||
Reference in new issue
Block a user