fix(fps): Epona jumps fences above a 60 fps cap #1434

Open
CraftyCorvid wants to merge 2 commits from CraftyCorvid/Longshot:fix/epona-jump-above-60 into main
Contributor

Type: fix · Risk: low · Tested on: Linux, RTX 5090 · Needs: none

Why

With the Game frame rate cap past 60, Epona doesn't jump fences: she starts the jump, but her animation keeps galloping and
she slides through the fence at ground level (her body goes over it, so she isn't stopped). At 70-90 fps it happened on
most jumps here, in one session on every one; the shorter the frames, the more often (the game-free test shows the cause
growing faster at 120 to 240 fps). At a cap of 60 she jumps as she should. No issue covers it (the tracker
searched for Epona, horse, jump, slow motion, blend); the other above-60 problems (#439, #988) are different places.

How to reproduce

Seen on: CachyOS Linux (kernel 7.3), RTX 5090, NVIDIA 620.70.06
Settings and switches: Game frame rate cap Uncapped (about 70-90 fps on this PC), everything else default
Steps: as adult Link, call Epona and ride her at a fence she jumps; do it 5 or 6 times
Expected: each time she leaps over the fence, as at a cap of 60
Actual: most times she gallops through it at ground level

What changed

A horse's jump state machine (f_82c59eb0) sets the blend frames into its JumpReady animation each frame, so the blend
ends at takeoff. On a step under 1, which at 60 fps is slow motion, it takes last frame's blend frames plus the step
instead. Above 60 fps every step is under 1, so the blend frames grew each frame (25 at 60 fps, 100 to 1500 above), the jump
animation never blended in, and Epona galloped on while her body jumped. The game's "step < 1" test now first asks
whether the step is the whole frame's (the game's time object's step); if it is, the slow-motion branch is skipped. A step
under the frame's (slow motion), a cap of 60 and a frame slower than 60 fps keep the game's own test.

  • lift: nx2/oot_patches.py patch_horse_jump: before f_82c59eb0's branch on fcmp s10, 1.0 (0x82c5ae1c), a call to
    hos_oot_horse_whole_step that takes the same branch (past the slow-motion one) when it returns 1; report warns when
    it is not found once.
  • host: host/oot_high_fps.h oot_horse_whole_step (the rule: above a 60 cap, a step within 0.1% of the frame's own,
    the frame's under 1) and host/oot_high_fps.c hos_oot_horse_whole_step (reads the time object's step, as the sound gate
    does; HOS_FPS_LOG counts it).
  • test: tests/test_horse_jump_step.py.
  • docs: the README's frame rate cap row.

How it was found: a diagnostic build (not in this PR) logged the jump decision, the controller, the animation layers and
the blend tree each frame around a jump. The jump starts the same way in good and bad jumps; the JumpReady blend weight
stayed under 0.01 at takeoff in the bad ones; a hardware watchpoint on it led to the blend node's interp frames, which read
animation variable 16, which the state machine writes in the branch above.

Measurements

Verdict: fixed. Every uncapped jump in the run after the fix cleared the fence with the jump animation (most slid through
before); the game-free test fails on main for this bug and passes here.

Hardware: CachyOS Linux (kernel 7.3), RTX 5090, NVIDIA 620.70.06
Scene: adult Link on Epona at fences; Game frame rate cap Uncapped (about 70-90 fps) and 60
Method: tests/test_horse_jump_step.py (gcc and clang); in the game, a diagnostic build on main's code logging the
animation variable the blend reads, then this branch played by hand
How to reproduce: python -I -B tests/test_horse_jump_step.py; in the game, the steps above
Baseline: measured on main 67efc4d3. main is now 50170f81, which adds only #1402 (the game's zstd decodes on the
host's libzstd); it touches none of the files or code this PR changes or reads. Rebased onto 50170f81 locally, the test
fails at the test commit and passes with the fix, and tests/run_all.py gives the same 602 passed and the same 33
failures: the numbers hold.

Before: main @ 67efc4d3 (with the test, dd5784ae) After: this PR @ 3293d6f7
test_horse_jump_step.py fails: the slow-motion branch runs every frame at 70, 120, 144 and 240 fps, blend frames 25 → 35-59 over 40 frames passes (13 checks, the unpatched update failing the 120 fps one)
JumpReady blend frames at takeoff, in the game (diagnostic build) cap 60: 25-27 (2 jumps); uncapped: 6-794 over 18 jumps, 91-794 in the 7 whose jump animation ended before landing (the failures), 6-117 in the other 11 not logged (no diagnostic build); uncapped, every jump cleared
Before, test (dd5784ae on main 67efc4d3):
FAIL: 120 fps: the slow-motion branch ran 40 of 40 frames, blend frames 45.000 (expected none, 25.000)
FAIL: 70 fps: the slow-motion branch ran 40 of 40 frames, blend frames 59.286 (expected none, 25.000)
FAIL: 144 fps: the slow-motion branch ran 40 of 40 frames, blend frames 41.667 (expected none, 25.000)
FAIL: 240 fps: the slow-motion branch ran 40 of 40 frames, blend frames 35.000 (expected none, 25.000)
FAIL: a horse's jump blend frames above 60 fps (the patch is missing)

After, test (3293d6f7):
PASS: a horse's jump blend frames (13 checks)
PASS: the unpatched update compiles and fails the 120 fps check (its blend frames grow by the step)
PASS: scoped, idempotent, and a changed anchor is left alone with a warning

Before, in the game (diagnostic build; s10 the step, s0 the blend frames written to variable 16):
cap 60:   horse: Sf SETVAR f417 st 2 fl 1.0369 b4 1.0148 | s0 27.2956 s8 23.9631 s9 26.6043 s10 1.0000 s11 25.0000 | w1 16
uncapped: horse: Sc getvar f4866 st 2 fl 7.8862 b4 1.1441 | s0 105.3844 s8 2.2357 s9 1.0000 s10 0.8043 s11 25.0000 | w1 16
          horse: Sf SETVAR f4866 st 2 fl 7.8862 b4 1.1441 | s0 106.1887 s8 17.1138 s9 106.1887 s10 0.8043 s11 25.0000 | w1 16

Flags and settings

None.

Testing

Tested:

  • tests/test_horse_jump_step.py with gcc and clang: fails at dd5784ae (the test alone on main), passes at 3293d6f7; with
    the new rule forced off the high-fps checks fail, forced on the slow-motion check fails.
  • python -I -B tests/run_all.py (Linux): 602 passed, 33 failed, 88 skipped (Vulkan and SPIR-V headers missing here). The
    33 also fail on main 67efc4d3, each run alone on both: test_bug_report_defaults, test_cpu_report, test_crt_options,
    test_damage_debug_menu, test_discover, test_display_startup_failure, test_dlss_feature_size,
    test_failed_compile_keeps_objects, test_framegen_preset, test_guest_imported, test_hud_layout_row, test_invalidate_vcore,
    test_lift_lookups, test_linux_preflight, test_linux_pressure, test_linux_update, test_mirror_budget, test_missing_nup,
    test_mods_size_table, test_pending_guest_import, test_pipeline_play_cache, test_present_thread, test_profiling_mode,
    test_readback_timeout_source, test_rumble_menu, test_run_all_changed, test_slow_frames, test_target_image_pool,
    test_upscaler_round_trip, test_upscaler_rows, test_vcore_escape, test_walk, test_walk_key.
  • host/oot_high_fps.c compiled alone (-fsyntax-only -Wall -Wextra, the build's include folders) with gcc and clang for
    Linux and with llvm-mingw clang (tools.lock's, 20261104) and MinGW gcc for Windows: no warnings, as on main.
  • In the game: Linux, RTX 5090, NVIDIA 620.70.06; this branch built as a dev pack over a base of 71b1edd8 (the lift reports
    "a horse's jump blend above 60 fps in code_040.c"). Riding Epona at fences uncapped (about 70-90 fps), every jump cleared
    the fence with the jump animation; at a cap of 60 the jumps were as before.

Not tested:

  • Windows in the game (the change has no platform-specific code; its host file compiles with llvm-mingw).
  • Above about 90 fps in the game (the game-free test covers 120, 144 and 240 fps).
  • Other horses that jump (Ingo's horse in the ranch races) and slow motion on horseback: they go through the same state
    machine; the game-free test covers slow motion above 60 fps.

Must be tested: None.

Risks

What could break: a horse's JumpReady blend above a 60 fps cap (Epona's, and any other horse's that uses this state
machine). A horse in slow motion above 60 fps keeps the game's branch only while its step is under the frame's by more
than 0.1%. At a cap of 60, and on frames slower than 60 fps, nothing changes: the host returns 0 and the game's own test
decides.

Turning it off: revert the commit, or a cap of 60.

Compatibility: Nothing changes for saves, options or caches; an update translates the game's code again, as for any
change to the lift's patches.

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • A game-free test added for the fix, failing on main and passing here.
  • A check under tests/ that reads changed source updated in this PR, not weakened. (None needed: the 27 checks that
    read host/oot_high_fps.* or nx2/oot_patches.py, test_high_fps_fixes.py and test_patch_hooks_defined.py among
    them, pass unchanged.)
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.
  • Docs updated.

🤖 Generated with Claude Code

**Type:** fix · **Risk:** low · **Tested on:** Linux, RTX 5090 · **Needs:** none ## Why With the Game frame rate cap past 60, Epona doesn't jump fences: she starts the jump, but her animation keeps galloping and she slides through the fence at ground level (her body goes over it, so she isn't stopped). At 70-90 fps it happened on most jumps here, in one session on every one; the shorter the frames, the more often (the game-free test shows the cause growing faster at 120 to 240 fps). At a cap of 60 she jumps as she should. No issue covers it (the tracker searched for Epona, horse, jump, slow motion, blend); the other above-60 problems (#439, #988) are different places. ## How to reproduce **Seen on:** CachyOS Linux (kernel 7.3), RTX 5090, NVIDIA 620.70.06 **Settings and switches:** Game frame rate cap Uncapped (about 70-90 fps on this PC), everything else default **Steps:** as adult Link, call Epona and ride her at a fence she jumps; do it 5 or 6 times **Expected:** each time she leaps over the fence, as at a cap of 60 **Actual:** most times she gallops through it at ground level ## What changed A horse's jump state machine (`f_82c59eb0`) sets the blend frames into its JumpReady animation each frame, so the blend ends at takeoff. On a step under 1, which at 60 fps is slow motion, it takes last frame's blend frames plus the step instead. Above 60 fps every step is under 1, so the blend frames grew each frame (25 at 60 fps, 100 to 1500 above), the jump animation never blended in, and Epona galloped on while her body jumped. The game's "step < 1" test now first asks whether the step is the whole frame's (the game's time object's step); if it is, the slow-motion branch is skipped. A step under the frame's (slow motion), a cap of 60 and a frame slower than 60 fps keep the game's own test. - lift: `nx2/oot_patches.py` `patch_horse_jump`: before `f_82c59eb0`'s branch on `fcmp s10, 1.0` (0x82c5ae1c), a call to `hos_oot_horse_whole_step` that takes the same branch (past the slow-motion one) when it returns 1; `report` warns when it is not found once. - host: `host/oot_high_fps.h` `oot_horse_whole_step` (the rule: above a 60 cap, a step within 0.1% of the frame's own, the frame's under 1) and `host/oot_high_fps.c` `hos_oot_horse_whole_step` (reads the time object's step, as the sound gate does; `HOS_FPS_LOG` counts it). - test: `tests/test_horse_jump_step.py`. - docs: the README's frame rate cap row. How it was found: a diagnostic build (not in this PR) logged the jump decision, the controller, the animation layers and the blend tree each frame around a jump. The jump starts the same way in good and bad jumps; the JumpReady blend weight stayed under 0.01 at takeoff in the bad ones; a hardware watchpoint on it led to the blend node's interp frames, which read animation variable 16, which the state machine writes in the branch above. ## Measurements **Verdict:** fixed. Every uncapped jump in the run after the fix cleared the fence with the jump animation (most slid through before); the game-free test fails on `main` for this bug and passes here. Hardware: CachyOS Linux (kernel 7.3), RTX 5090, NVIDIA 620.70.06 Scene: adult Link on Epona at fences; Game frame rate cap Uncapped (about 70-90 fps) and 60 Method: `tests/test_horse_jump_step.py` (gcc and clang); in the game, a diagnostic build on `main`'s code logging the animation variable the blend reads, then this branch played by hand How to reproduce: `python -I -B tests/test_horse_jump_step.py`; in the game, the steps above Baseline: measured on `main` 67efc4d3. `main` is now 50170f81, which adds only #1402 (the game's zstd decodes on the host's libzstd); it touches none of the files or code this PR changes or reads. Rebased onto 50170f81 locally, the test fails at the test commit and passes with the fix, and `tests/run_all.py` gives the same 602 passed and the same 33 failures: the numbers hold. | | Before: main @ 67efc4d3 (with the test, dd5784ae) | After: this PR @ 3293d6f7 | |---|---|---| | `test_horse_jump_step.py` | fails: the slow-motion branch runs every frame at 70, 120, 144 and 240 fps, blend frames 25 → 35-59 over 40 frames | passes (13 checks, the unpatched update failing the 120 fps one) | | JumpReady blend frames at takeoff, in the game (diagnostic build) | cap 60: 25-27 (2 jumps); uncapped: 6-794 over 18 jumps, 91-794 in the 7 whose jump animation ended before landing (the failures), 6-117 in the other 11 | not logged (no diagnostic build); uncapped, every jump cleared | ``` Before, test (dd5784ae on main 67efc4d3): FAIL: 120 fps: the slow-motion branch ran 40 of 40 frames, blend frames 45.000 (expected none, 25.000) FAIL: 70 fps: the slow-motion branch ran 40 of 40 frames, blend frames 59.286 (expected none, 25.000) FAIL: 144 fps: the slow-motion branch ran 40 of 40 frames, blend frames 41.667 (expected none, 25.000) FAIL: 240 fps: the slow-motion branch ran 40 of 40 frames, blend frames 35.000 (expected none, 25.000) FAIL: a horse's jump blend frames above 60 fps (the patch is missing) After, test (3293d6f7): PASS: a horse's jump blend frames (13 checks) PASS: the unpatched update compiles and fails the 120 fps check (its blend frames grow by the step) PASS: scoped, idempotent, and a changed anchor is left alone with a warning Before, in the game (diagnostic build; s10 the step, s0 the blend frames written to variable 16): cap 60: horse: Sf SETVAR f417 st 2 fl 1.0369 b4 1.0148 | s0 27.2956 s8 23.9631 s9 26.6043 s10 1.0000 s11 25.0000 | w1 16 uncapped: horse: Sc getvar f4866 st 2 fl 7.8862 b4 1.1441 | s0 105.3844 s8 2.2357 s9 1.0000 s10 0.8043 s11 25.0000 | w1 16 horse: Sf SETVAR f4866 st 2 fl 7.8862 b4 1.1441 | s0 106.1887 s8 17.1138 s9 106.1887 s10 0.8043 s11 25.0000 | w1 16 ``` ### Flags and settings None. ## Testing **Tested:** - `tests/test_horse_jump_step.py` with gcc and clang: fails at dd5784ae (the test alone on `main`), passes at 3293d6f7; with the new rule forced off the high-fps checks fail, forced on the slow-motion check fails. - `python -I -B tests/run_all.py` (Linux): 602 passed, 33 failed, 88 skipped (Vulkan and SPIR-V headers missing here). The 33 also fail on `main` 67efc4d3, each run alone on both: test_bug_report_defaults, test_cpu_report, test_crt_options, test_damage_debug_menu, test_discover, test_display_startup_failure, test_dlss_feature_size, test_failed_compile_keeps_objects, test_framegen_preset, test_guest_imported, test_hud_layout_row, test_invalidate_vcore, test_lift_lookups, test_linux_preflight, test_linux_pressure, test_linux_update, test_mirror_budget, test_missing_nup, test_mods_size_table, test_pending_guest_import, test_pipeline_play_cache, test_present_thread, test_profiling_mode, test_readback_timeout_source, test_rumble_menu, test_run_all_changed, test_slow_frames, test_target_image_pool, test_upscaler_round_trip, test_upscaler_rows, test_vcore_escape, test_walk, test_walk_key. - `host/oot_high_fps.c` compiled alone (`-fsyntax-only -Wall -Wextra`, the build's include folders) with gcc and clang for Linux and with llvm-mingw clang (tools.lock's, 20261104) and MinGW gcc for Windows: no warnings, as on `main`. - In the game: Linux, RTX 5090, NVIDIA 620.70.06; this branch built as a dev pack over a base of 71b1edd8 (the lift reports "a horse's jump blend above 60 fps in code_040.c"). Riding Epona at fences uncapped (about 70-90 fps), every jump cleared the fence with the jump animation; at a cap of 60 the jumps were as before. **Not tested:** - Windows in the game (the change has no platform-specific code; its host file compiles with llvm-mingw). - Above about 90 fps in the game (the game-free test covers 120, 144 and 240 fps). - Other horses that jump (Ingo's horse in the ranch races) and slow motion on horseback: they go through the same state machine; the game-free test covers slow motion above 60 fps. **Must be tested:** None. ## Risks **What could break:** a horse's JumpReady blend above a 60 fps cap (Epona's, and any other horse's that uses this state machine). A horse in slow motion above 60 fps keeps the game's branch only while its step is under the frame's by more than 0.1%. At a cap of 60, and on frames slower than 60 fps, nothing changes: the host returns 0 and the game's own test decides. **Turning it off:** revert the commit, or a cap of 60. **Compatibility:** Nothing changes for saves, options or caches; an update translates the game's code again, as for any change to the lift's patches. ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] A game-free test added for the fix, failing on `main` and passing here. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. (None needed: the 27 checks that read `host/oot_high_fps.*` or `nx2/oot_patches.py`, `test_high_fps_fixes.py` and `test_patch_hooks_defined.py` among them, pass unchanged.) - [x] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
While a horse gets ready to jump an obstacle, its jump state machine
(f_82c59eb0) sets each frame the blend frames into its JumpReady
animation, and with a step under 1 (slow motion at 60 fps) it takes
them from last frame's plus the step. Above 60 fps every step is under
1, so they grow each frame and Epona gallops through the fence.

An authored update with the step test's two anchor lines goes through
patch_file and is run frame by frame. Fails on main: at 70, 120, 144
and 240 fps the slow-motion branch runs every frame and the blend
frames grow from 25 to 35-59.

Assisted-by: Claude Code (Claude Opus 5.5)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
fix(fps): Epona jumps fences above a 60 fps cap
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 9s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
3293d6f7bb
A horse's jump state machine (f_82c59eb0) sets each frame, while the
horse gets ready to jump, the blend frames into its JumpReady
animation, so the blend ends at takeoff. On a step under 1 (slow
motion at 60 fps) it takes them from last frame's plus the step
instead. Above 60 fps every step is under 1: the blend frames grew by
the step each frame (25 at 60 fps, 100 to 1500 above), the jump
animation never blended in, and Epona galloped through the fence at
ground level while her body went over it. Around 60 to 90 fps it
happened only when no frame's step reached 1.

Before the branch on its "step < 1" test, hos_oot_horse_whole_step
sends a step that is the whole frame's (the game's time object, +0x10)
past the slow-motion branch too (nx2/oot_patches.py patch_horse_jump,
host/oot_high_fps.h oot_horse_whole_step). A step under the frame's
(slow motion), a cap of 60 and a frame slower than 60 fps keep the
game's own test.

Assisted-by: Claude Code (Claude Opus 5.5)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Contributor

Tested in game: Linux (CachyOS, kernel 7.3), RTX 5090, NVIDIA 620.70.06; this branch as a dev pack over a base of 71b1edd8. Riding Epona at fences with the Game frame rate cap Uncapped (about 70-90 fps): every jump cleared the fence with the jump animation (on main most of them slid through at ground level). At a cap of 60 the jumps were as before.

Tested in game: Linux (CachyOS, kernel 7.3), RTX 5090, NVIDIA 620.70.06; this branch as a dev pack over a base of 71b1edd8. Riding Epona at fences with the Game frame rate cap Uncapped (about 70-90 fps): every jump cleared the fence with the jump animation (on main most of them slid through at ground level). At a cap of 60 the jumps were as before.
CraftyCorvid force-pushed fix/epona-jump-above-60 from 3293d6f7bb
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 9s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
to e04c08065a
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
PR description / Description follows the template (pull_request_target) Successful in 3s
2026-11-17 17:07:20 +00:00
Compare
CraftyCorvid changed title from WIP: fix(fps): Epona jumps fences above a 60 fps cap to fix(fps): Epona jumps fences above a 60 fps cap 2026-11-17 17:08:02 +00:00
Author
Contributor

Measured on main 67efc4d3; main is now 50170f81, which adds only #1402 (zstd decodes on the host's libzstd) and touches none of this PR's files. Rebased onto it locally: the new test fails at the test commit and passes with the fix, and run_all gives the same 602 passed and the same 33 failures as on main. The numbers hold; the Measurements section now says so.

Measured on main 67efc4d3; main is now 50170f81, which adds only #1402 (zstd decodes on the host's libzstd) and touches none of this PR's files. Rebased onto it locally: the new test fails at the test commit and passes with the fix, and run_all gives the same 602 passed and the same 33 failures as on main. The numbers hold; the Measurements section now says so.
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
PR description / Description follows the template (pull_request_target) Successful in 3s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
Some workflows are waiting to be reviewed.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'fix/epona-jump-above-60:CraftyCorvid-fix/epona-jump-above-60'
git switch 'CraftyCorvid-fix/epona-jump-above-60'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1434
No description provided.