WIP: fix(fps): the frozen Zoras stand still above a 60 fps cap #1444

Draft
cuecuemoar wants to merge 3 commits from cuecuemoar/Longshot:fix/frozen-zora-above-60 into main
Contributor

Type: fix · Risk: low · Tested on: Windows 10, RTX 4090 · Needs: none

Why

The frozen Zoras under the ice in Zora's Domain (the big pond in the first cavern, as the adult) are meant to stand still. With the Game frame rate cap above 60 they twitch back and forth instead; at a cap of 60 they are completely still. Fixes #988.

How to reproduce

Seen on: Windows 10, RTX 4090, NVIDIA driver 32.0.16.1742
Settings and switches: Game frame rate cap Uncapped (about 110 fps in the scene), Render resolution 50%, otherwise defaults
Steps: load a save as the adult, go to Zora's Domain, walk to the first cavern's pond and look at the frozen Zoras under the ice (about [17-24, 100, -7..0])
Expected: the Zoras stand still, as at a cap of 60
Actual: on main they vibrate; set the cap to 60 and they stop

What changed

A loop of one frame (the Zoras: start 0, end 1) is one pose. At 60 fps the clock's step is 1, so every update lands on the same phase. Above 60 the step is the frame's own time (0.36 at 165 fps); the phase moved by it each frame and wrapped, so each frame drew another phase of the loop. The change keeps a loop of one frame or less on whole frames above 60, and leaves longer loops and a cap of 60 as they are.

  • nx2/oot_patches.py: patch_loop_steps patches the two clock advances of f_802cfca0 (each animation entry's time +4, start +16, end +20) to take the step from hos_loop_step; patch_loop_pose patches the one store of the skeleton's drawn time in f_80944aa0 (the value +0 and the range it is kept in +4, +8) to hos_loop_pose. Both leave a file whose code differs, or that is patched already, as it is.
  • host/loop_step.h: the logic. loop_step hands out whole frames of the step for an entry whose loop is one frame or less (end > start, end - start <= 1), the fractions carried per entry (4096 slots found by address); loop_pose returns the loop's start for such a range. Both do nothing at a cap of 60.
  • host/nn_vi.c: hos_loop_step and hos_loop_pose, the entry points the patches call; the lock is taken only for a loop of one frame or less.
  • tests/test_loop_step.py: the game-free test.
  • README.md: one line next to the known above-60 notes.
  • docs/tested/: one file for each run below.

Measurements

Verdict: the Zoras twitch on main Uncapped and stand still with this change at the same frame rate, by eye; nothing else in the room looked different. A GIF of 24 consecutive shots of each build is in the comment of 2026-11-17 18:09, with the change of the area beside Link measured on them (table); the game-free test below holds the phase of the loop over a second at 165 fps.

Baseline: main e090cc48 is the dev base the pack was built over; the After build (a pack over it) carried all of main up to this branch, main 50170f81 included (zstd decodes, the switch table, perf summaries: nothing in the animation or step code), so the Before and After differ by this change.

Hardware: Windows 10 Pro, RTX 4090, driver 32.0.16.1742, i9-13900K, 32 GB
Scene: adult Zora's Domain, the frozen Zoras about 10 units away; Render resolution 50%, Frame rate cap Uncapped
Method: looked at by eye through the game's window, scripts/longshot_ctl.py launch --profile default, teleport 13 and a walk to the pond; no forced step
How to reproduce: as above

Before: main @ e090cc48 After: this PR @ ca4f19bd
Zoras, Uncapped (about 110 fps) twitch (a vibrating back and forth) still
Zoras, cap 60 still not run (the change does nothing at 60)
the rest of the room (water, ice, lights) not looked at nothing different
area beside Link over 24 consecutive shots (the GIF in the comment): mean absolute change per frame pair 0.46 0.18
same area: pixels per pair changing by more than 12 levels 135 2

The test (python -I -B tests/test_loop_step.py), on the test commit alone (Before: main @ e592609f, the fix not in the tree) and on the branch (After: this PR @ ca4f19bd):

Before: main @ e592609f
FAIL: a loop of one frame must stay on one phase at 165 fps (2 times)
FAIL: each loop of one frame keeps its own phase (300 times)
FAIL: the loop from 2 to 3 is a pose too (2 times)
FAIL: a loop of one frame is drawn at its start (1 times)
FAIL: a loop of one frame is drawn at its own start (1 times)
After: this PR @ ca4f19bd
PASS: loop of one frame
PASS: the unpatched updates are rejected by the same checks

Flags and settings

None.

Testing

Tested:

  • tests/test_loop_step.py compiles the production patches on authored updates and the real host/loop_step.h, and holds: a loop of one frame stays on one phase at 165 fps (both clock sites, two entries in turn each keeping their own phase), a loop from 2 to 3 is a pose too, a loop of a frame and a half and a loop of 1000 frames keep the fractional step, a cap of 60 and a paused clock are as the game has them, the drawn time is the start only for a loop of one frame or less. It fails on main (above) and fails on six deliberately broken fixes (no whole frames, the pose left as the time, the cap of 60 ignored in either function, long loops made whole, the second clock site not patched). The patches are idempotent and leave an unrelated authored function alone.
  • python -I -B tests/run_all.py on this branch and on main 50170f81, the same PC: the same 44 checks fail on both (a missing clang, Vulkan headers and the like on this WSL); this branch adds test_loop_step (passes). test_xess_rules timed out in the first branch run while the game was running at the same time, and passes alone.
  • In the game, Windows 10 Pro, RTX 4090, driver 32.0.16.1742: the pack built from ca4f19bd (every patch applied: the lift log shows "2 animation clock(s) with whole frames for a loop of one frame in code_002.c" and "the drawn time of a loop of one frame by its start in code_008.c") against main e090cc48, adult Zora's Domain, Uncapped at about 110 fps: main twitches, this stands still (table above).

Not tested: Linux, AMD or Intel; other scenes with a loop of one frame or less (the change applies to every skeleton whose animation clock or drawn-time range is one frame or less above a cap of 60, which at 60 fps stands on one phase too, so those should only match 60 fps; Zora's Domain is the only place looked at); caps other than Uncapped above 60.

Must be tested: None. (Optional, other hardware: adult Zora's Domain, first cavern pond, Frame rate cap Uncapped or 144 with the frame rate above 60, looking at the frozen Zoras under the ice: they should stand still.)

Risks

What could break: a skeleton whose animation is meant to move within a range of one frame or less would stand still above 60, as it already does at 60 fps (step 1 lands on one phase there). Nothing else is touched: longer loops and a cap of 60 take the game's own step and time.

Turning it off: revert the commit; a cap of 60 never takes the new path.

Compatibility: nothing changes for saves, longshot_options.ini, the shader and pipeline caches or the vk ABI; the lifted game is lifted again with the two patches.

Issues

Fixes #988

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).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main (50170f81).
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named): the same 44 checks fail on main, named above.
  • 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.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen: a GIF of 24 consecutive shots, main (Before: main @ e090cc48) beside this PR (After: this PR @ ca4f19bd), in the comment of 2026-11-17 18:09.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md).
  • A game-free test added for the fix, failing on main and passing here.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths: Windows built (the pack above); host/loop_step.h is plain C and is compiled by gcc on Linux in the test; host/nn_vi.c was not built on Linux (its new lock is the same SRWLOCK use as hos_frame_whole beside it).
  • Docs updated.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VxeaZkHkexryjX95trtxhH

**Type:** fix · **Risk:** low · **Tested on:** Windows 10, RTX 4090 · **Needs:** none ## Why The frozen Zoras under the ice in Zora's Domain (the big pond in the first cavern, as the adult) are meant to stand still. With the Game frame rate cap above 60 they twitch back and forth instead; at a cap of 60 they are completely still. Fixes #988. ## How to reproduce **Seen on:** Windows 10, RTX 4090, NVIDIA driver 32.0.16.1742 **Settings and switches:** Game frame rate cap Uncapped (about 110 fps in the scene), Render resolution 50%, otherwise defaults **Steps:** load a save as the adult, go to Zora's Domain, walk to the first cavern's pond and look at the frozen Zoras under the ice (about [17-24, 100, -7..0]) **Expected:** the Zoras stand still, as at a cap of 60 **Actual:** on main they vibrate; set the cap to 60 and they stop ## What changed A loop of one frame (the Zoras: start 0, end 1) is one pose. At 60 fps the clock's step is 1, so every update lands on the same phase. Above 60 the step is the frame's own time (0.36 at 165 fps); the phase moved by it each frame and wrapped, so each frame drew another phase of the loop. The change keeps a loop of one frame or less on whole frames above 60, and leaves longer loops and a cap of 60 as they are. - `nx2/oot_patches.py`: `patch_loop_steps` patches the two clock advances of `f_802cfca0` (each animation entry's time +4, start +16, end +20) to take the step from `hos_loop_step`; `patch_loop_pose` patches the one store of the skeleton's drawn time in `f_80944aa0` (the value +0 and the range it is kept in +4, +8) to `hos_loop_pose`. Both leave a file whose code differs, or that is patched already, as it is. - `host/loop_step.h`: the logic. `loop_step` hands out whole frames of the step for an entry whose loop is one frame or less (`end > start`, `end - start <= 1`), the fractions carried per entry (4096 slots found by address); `loop_pose` returns the loop's start for such a range. Both do nothing at a cap of 60. - `host/nn_vi.c`: `hos_loop_step` and `hos_loop_pose`, the entry points the patches call; the lock is taken only for a loop of one frame or less. - `tests/test_loop_step.py`: the game-free test. - `README.md`: one line next to the known above-60 notes. - `docs/tested/`: one file for each run below. ## Measurements **Verdict:** the Zoras twitch on main Uncapped and stand still with this change at the same frame rate, by eye; nothing else in the room looked different. A GIF of 24 consecutive shots of each build is in the comment of 2026-11-17 18:09, with the change of the area beside Link measured on them (table); the game-free test below holds the phase of the loop over a second at 165 fps. Baseline: main e090cc48 is the dev base the pack was built over; the After build (a pack over it) carried all of main up to this branch, main 50170f81 included (zstd decodes, the switch table, perf summaries: nothing in the animation or step code), so the Before and After differ by this change. Hardware: Windows 10 Pro, RTX 4090, driver 32.0.16.1742, i9-13900K, 32 GB Scene: adult Zora's Domain, the frozen Zoras about 10 units away; Render resolution 50%, Frame rate cap Uncapped Method: looked at by eye through the game's window, `scripts/longshot_ctl.py launch --profile default`, `teleport 13` and a walk to the pond; no forced step How to reproduce: as above | | Before: main @ e090cc48 | After: this PR @ ca4f19bd | |---|---|---| | Zoras, Uncapped (about 110 fps) | twitch (a vibrating back and forth) | still | | Zoras, cap 60 | still | not run (the change does nothing at 60) | | the rest of the room (water, ice, lights) | not looked at | nothing different | | area beside Link over 24 consecutive shots (the GIF in the comment): mean absolute change per frame pair | 0.46 | 0.18 | | same area: pixels per pair changing by more than 12 levels | 135 | 2 | The test (`python -I -B tests/test_loop_step.py`), on the test commit alone (Before: main @ e592609f, the fix not in the tree) and on the branch (After: this PR @ ca4f19bd): ``` Before: main @ e592609f FAIL: a loop of one frame must stay on one phase at 165 fps (2 times) FAIL: each loop of one frame keeps its own phase (300 times) FAIL: the loop from 2 to 3 is a pose too (2 times) FAIL: a loop of one frame is drawn at its start (1 times) FAIL: a loop of one frame is drawn at its own start (1 times) After: this PR @ ca4f19bd PASS: loop of one frame PASS: the unpatched updates are rejected by the same checks ``` ### Flags and settings None. ## Testing **Tested:** - `tests/test_loop_step.py` compiles the production patches on authored updates and the real `host/loop_step.h`, and holds: a loop of one frame stays on one phase at 165 fps (both clock sites, two entries in turn each keeping their own phase), a loop from 2 to 3 is a pose too, a loop of a frame and a half and a loop of 1000 frames keep the fractional step, a cap of 60 and a paused clock are as the game has them, the drawn time is the start only for a loop of one frame or less. It fails on main (above) and fails on six deliberately broken fixes (no whole frames, the pose left as the time, the cap of 60 ignored in either function, long loops made whole, the second clock site not patched). The patches are idempotent and leave an unrelated authored function alone. - `python -I -B tests/run_all.py` on this branch and on main 50170f81, the same PC: the same 44 checks fail on both (a missing clang, Vulkan headers and the like on this WSL); this branch adds `test_loop_step` (passes). `test_xess_rules` timed out in the first branch run while the game was running at the same time, and passes alone. - In the game, Windows 10 Pro, RTX 4090, driver 32.0.16.1742: the pack built from `ca4f19bd` (every patch applied: the lift log shows "2 animation clock(s) with whole frames for a loop of one frame in code_002.c" and "the drawn time of a loop of one frame by its start in code_008.c") against main e090cc48, adult Zora's Domain, Uncapped at about 110 fps: main twitches, this stands still (table above). **Not tested:** Linux, AMD or Intel; other scenes with a loop of one frame or less (the change applies to every skeleton whose animation clock or drawn-time range is one frame or less above a cap of 60, which at 60 fps stands on one phase too, so those should only match 60 fps; Zora's Domain is the only place looked at); caps other than Uncapped above 60. **Must be tested:** None. (Optional, other hardware: adult Zora's Domain, first cavern pond, Frame rate cap Uncapped or 144 with the frame rate above 60, looking at the frozen Zoras under the ice: they should stand still.) ## Risks **What could break:** a skeleton whose animation is meant to move within a range of one frame or less would stand still above 60, as it already does at 60 fps (step 1 lands on one phase there). Nothing else is touched: longer loops and a cap of 60 take the game's own step and time. **Turning it off:** revert the commit; a cap of 60 never takes the new path. **Compatibility:** nothing changes for saves, `longshot_options.ini`, the shader and pipeline caches or the vk ABI; the lifted game is lifted again with the two patches. ## Issues Fixes #988 ## 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] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main` (50170f81). - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named): the same 44 checks fail on main, named above. - [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] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen: a GIF of 24 consecutive shots, main (Before: main @ e090cc48) beside this PR (After: this PR @ ca4f19bd), in the comment of 2026-11-17 18:09. - [x] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [x] A game-free test added for the fix, failing on `main` and passing here. - [ ] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths: Windows built (the pack above); `host/loop_step.h` is plain C and is compiled by gcc on Linux in the test; `host/nn_vi.c` was not built on Linux (its new lock is the same `SRWLOCK` use as `hos_frame_whole` beside it). - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01VxeaZkHkexryjX95trtxhH
The frozen Zoras under the ice in adult Zora's Domain loop over one frame (start 0, end 1). At 60 fps the clock's step is 1 and they stand on one phase; above a 60 cap the step is the frame's own time (0.36 at 165 fps), each frame draws another phase and they twitch.

Compiles the production patches on authored updates (f_802cfca0's clock advance, f_80944aa0's time write) with host/loop_step.h's functions: it fails on main (the phase moves every frame, the time is not the loop's start) and the same checks hold the long loops, a cap of 60 and a paused clock as the game has them.

Assisted-by: Claude Code (claude-sonnet-5-5)
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VxeaZkHkexryjX95trtxhH
A loop of one frame (the Zoras under the ice in adult Zora's Domain: start 0, end 1) is one pose. At 60 fps the animation clock's step is 1 and every update lands on the same phase. Above a 60 cap the step is the frame's own time (0.36 at 165 fps), the clock moved by it each frame and wrapped, so each frame drew another phase and the Zoras twitched.

The time a skeleton is drawn at is made in two places, both patched at lift time (nx2/oot_patches.py):
- f_802cfca0 advances the clock of each animation entry in two places that multiply the step: a loop of one frame or less takes the step as whole frames with the remainder carried per entry (hos_loop_step), the rest keep the fractional step;
- f_80944aa0 writes the time the skeletons are drawn at from a clock of its own that also moved by the fractional step: a range of one frame or less is drawn at its start (hos_loop_pose).
host/loop_step.h holds the logic, host/nn_vi.c the locked entry points. A cap of 60 leaves both as the game has them.

Assisted-by: Claude Code (claude-sonnet-5-5)
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VxeaZkHkexryjX95trtxhH
docs(tested): the frozen Zoras on main and with the fix, Uncapped (#988)
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
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 8s
b1f953ccd9
One file a run: main e090cc48 (the Zoras twitch Uncapped, still at 60) and this branch (still Uncapped), both by eye in adult Zora's Domain at about 110 fps.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VxeaZkHkexryjX95trtxhH
Author
Contributor

Tested in game: Windows 10 Pro, RTX 4090, NVIDIA driver 32.0.16.1742: adult Zora's Domain, the frozen Zoras under the first cavern's pond, Frame rate cap Uncapped at about 110 fps. main e090cc48: they twitch (still at a cap of 60); this branch's code (ca4f19bd, built as a pack, no probes): they stand still and nothing else in the room looked different. Both watched by eye.

Tested in game: Windows 10 Pro, RTX 4090, NVIDIA driver 32.0.16.1742: adult Zora's Domain, the frozen Zoras under the first cavern's pond, Frame rate cap Uncapped at about 110 fps. main e090cc48: they twitch (still at a cap of 60); this branch's code (ca4f19bd, built as a pack, no probes): they stand still and nothing else in the room looked different. Both watched by eye.
Author
Contributor

@Beanstalk linux: please build this PR on Linux (host/nn_vi.c and the new host/loop_step.h are the host code it changes; the PR's Linux-build box waits on this) and, if the farm can run the game, look at the frozen Zoras in adult Zora's Domain (under the ice of the first cavern's pond) with the Game frame rate cap Uncapped or 144 and the frame rate above 60: they should stand still (on main they vibrate).

@Beanstalk linux: please build this PR on Linux (host/nn_vi.c and the new host/loop_step.h are the host code it changes; the PR's Linux-build box waits on this) and, if the farm can run the game, look at the frozen Zoras in adult Zora's Domain (under the ice of the first cavern's pond) with the Game frame rate cap Uncapped or 144 and the frame rate above 60: they should stand still (on main they vibrate).
Member

@cuecuemoar only members of BigBeans can start the farm. One of them can approve this request by reacting 👍 to it or to this comment.

@cuecuemoar only members of `BigBeans` can start the farm. One of them can approve this request by reacting 👍 to it or to this comment.
Author
Contributor

The frozen Zoras on consecutive frames, Uncapped (about 115 fps), the same spot in adult Zora's Domain on each build (Link at about [18.9, 100.0, -7.9] on main and [18.8, 100.0, -7.0] on this PR). Left: Before: main @ e090cc48. Right: After: this PR @ ca4f19bd.

the area beside Link on 24 consecutive shots, main on the left and this PR on the right

How it was made: 24 shots from the control bridge, each the first present after the last one's frame (4 presents apart, about 35 ms, so the GIF at 8 fps is about 3.5 times slower than the game), cropped beside Link and shown with one fixed contrast stretch for both builds (the ice is murky from above, and a per-frame stretch would flicker by itself). Link's idle animation moves on both.

Measured over the same 24 shots, in a 240 by 290 pixel window beside Link (where the Zoras are; 1920x1080 window, Render resolution 50%):

Before: main @ e090cc48 After: this PR @ ca4f19bd
mean absolute change per frame pair 0.46 0.18
pixels per pair changing by more than 12 levels 135 2
The frozen Zoras on consecutive frames, Uncapped (about 115 fps), the same spot in adult Zora's Domain on each build (Link at about [18.9, 100.0, -7.9] on main and [18.8, 100.0, -7.0] on this PR). Left: Before: main @ e090cc48. Right: After: this PR @ ca4f19bd. ![the area beside Link on 24 consecutive shots, main on the left and this PR on the right](https://git.magicbean.dev/attachments/cb52c6c3-5550-4043-b2af-247888d8fa45) How it was made: 24 shots from the control bridge, each the first present after the last one's frame (4 presents apart, about 35 ms, so the GIF at 8 fps is about 3.5 times slower than the game), cropped beside Link and shown with one fixed contrast stretch for both builds (the ice is murky from above, and a per-frame stretch would flicker by itself). Link's idle animation moves on both. Measured over the same 24 shots, in a 240 by 290 pixel window beside Link (where the Zoras are; 1920x1080 window, Render resolution 50%): | | Before: main @ e090cc48 | After: this PR @ ca4f19bd | |---|---|---| | mean absolute change per frame pair | 0.46 | 0.18 | | pixels per pair changing by more than 12 levels | 135 | 2 |
Owner

Brought up to the ready-for-review standard (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know).

  • Tested on my own PC: ticked: Testing's Tested: an in-game run on Windows 10, RTX 4090, watched by eye.
  • Nothing gets worse that I know of: ticked: Measurements gives a by-eye verdict, and Risks names no speed, latency or memory cost.
Brought up to the [ready-for-review standard](https://git.magicbean.dev/MagicBeanDev/Longshot/src/branch/main/CONTRIBUTING.md#ready-for-review-out-of-wip) (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know). - *Tested on my own PC*: ticked: Testing's Tested: an in-game run on Windows 10, RTX 4090, watched by eye. - *Nothing gets worse that I know of*: ticked: Measurements gives a by-eye verdict, and Risks names no speed, latency or memory cost.
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
Website / Website on Cloudflare (pull_request_target) Has been skipped
beanstalk/approval waiting for a BigBean's 👍 on the request
PR description / Description follows the template (pull_request_target) Successful in 8s
This pull request is marked as a work in progress.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'fix/frozen-zora-above-60:cuecuemoar-fix/frozen-zora-above-60'
git switch 'cuecuemoar-fix/frozen-zora-above-60'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
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!1444
No description provided.