Make a moving floor carry Link above 100 fps as it does at 60 (set ofollow, floor_carry = 1).

The character controller's three follow-surface modules kept only a tenth of the floor's velocity whenever the physics' inverse step passed 100, which every update above 100 fps did. The gate now compares with 100 over frames per update from the patch page above 60 fps, and with the game's 100 at 60 and 30 fps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-13 07:07:34 -05:00
parent d9429b0c00
commit c84724da2c
7 changed files with 149 additions and 8 deletions

View File

@@ -471,7 +471,10 @@ the water managers and floors of the set `owater` get 60 fixed steps a second wi
frame gives what the game computes. It also checks that each of those sites in `recomp/patches-v111.txt` ends in one
`bl` to its page slot, and runs the physics solver step count's words of the original and the sets `osolver` and
`osolverfull` (`physics_steps` 0, 1 and 2), lifted as the generator lifts them: the game's 4 and 8 at 60 and 30 fps
for all three, rounded up by `osolver` and at least 4 every update by `osolverfull` above 60 fps. No game files.
for all three, rounded up by `osolver` and at least 4 every update by `osolverfull` above 60 fps. For the set `ofollow`
(`floor_carry`) it checks the two words of each of the three floor-carry gates and runs the gate's compare with the
game's words and the set's: the page's cut is 100 at 60 and 30 fps, and from 90 to 240 fps the set cuts a floor's
velocity at the time scales where the game cuts it at 60 fps and nowhere else. No game files.
A change to how the mixer applies volumes (`runtime/audio_mixer.c` `accumulate_ramp`, the voice and splitter paths
of `audio_mixer_render`) or to what it owes the device after a stall (`ring_pull`, `audio_mixer_owed`) passes