fix(fps): Link's cap and other cloth keep the game's clock below 60 fps #1384

Open
dukenheimer wants to merge 4 commits from dukenheimer/Longshot:fix/hat-cloth-low-fps into main
Contributor

Type: fix · Risk: low · Tested on: Windows 11, RTX 5090; Steam Deck OLED (SteamOS, RADV) · Needs: none

TL;DR

Below 60 fps Link's cap floats: after he stops it swings far out and takes about a second to settle, because the game steps
the cloth a 60th of a second a frame however long the frame was. This makes the cloth step as far as the rest of the game
when frames are slow, so the cap settles about as at 60 fps. Checked at 18 fps on a PC and on the Steam Deck, with no
measurable CPU cost and nothing unstable seen in four areas, the pause menu and two area changes.

Breakdown

  • Who it helps: anyone below 60 fps, above all on the Steam Deck (17 to 24 fps).
  • What was wrong: the Havok cloth (Link's cap, NPC clothes) advanced 1/60 s a frame while the game advanced its frame
    step (3.3/60 s at 18 fps), so the cloth lagged behind Link and over-swung.
  • What changes: while the engine's frame step is over 1, the cloth's time a frame is the step's 60ths; HOS_FPS_CLOTH=0
    turns it off.
  • What doesn't change: at a step of 1 or less (60 fps and above) nothing; the solve count; the fixed-1/60 cloth mode.
  • How it was checked: a game-free test failing on main; at 18 fps on Windows (3 interleaved CPU pairs, stills in Kokiri
    Forest, Hyrule Field, Kakariko, the pause menu and area changes) and on the Steam Deck (2 runs a side, stills).
  • Still open: cloth above 60 fps (a separate change); other areas, cutscenes and NPC clothes up close weren't checked.
  • Risk: low: cloth steps up to 4 times as long at the lowest frame rates; no instability seen; one switch to turn it off.

Why

When the game runs below 60 fps, Link's cap floats: after he stops, it swings far out to the side and takes about a second to
settle. On the Steam Deck (17 to 24 fps) players see it all the time. At 60 fps it settles in about 0.2 s.

The cap is Havok cloth, and the game steps it a fixed 1/60 of a second each frame, whatever the game's own frame step for that
frame. With an engine frame step of 3.3 (about 18 fps), the cloth advances 1/60 s while the rest of the game advances 3.3/60 s,
about 0.3 of it. So the cloth lags behind Link: each cloth step sees his head move about 3.3 times as far, the cap swings wide,
and its settling takes about 3.3 times as long in real time. On a fast PC held to 18 fps it looks the same, so the frame step
alone causes it. The console would step the cloth the same way whenever its frame-rate controller drops to 30, 20 or 15 fps,
so this improves on the original's behaviour at low frame rates.

How to reproduce

Seen on: Windows 11, RTX 5090 (NVIDIA 621.14); the Steam Deck (reported)
Settings and switches: defaults at the game's 60 cap; HOS_FRAME_SLEEP_MS=53 (about 18 fps) on a fast PC, or any PC or
Deck that runs under 30 fps
Steps: in Kokiri Forest, run Link forward for 2 s and let go of the stick.
Expected: the cap follows his head and settles within about 0.2 s after he stops, as at 60 fps.
Actual: on main, the cap's tail flares out sideways 0.2 to 0.45 s after the stop and takes about a second to settle.

What changed

While the engine's frame step is over 1, the cloth's simulate setup steps by the game's 1/60 times that step, so the cloth
advances as far as the rest of the game that frame. The solve count stays the same. With a step of 1 or less nothing changes
(at 60 fps and above; a 60-capped game can still have steps over 1 on slow frames, and those are scaled). The cloth above
60 fps, which still steps 1/60 a frame, is left for a separate change.

  • nx2/oot_patches.py patch_cloth_time:
    • In f_81b3aa48, the Havok simulate operator's per-frame setup, the load of the step context's time (+8) goes through
      hos_oot_cloth_seconds with the engine's frame step: the float f_83b6ea90 writes at 0x84d61fc8, 60 / its frame rate.
    • The setup stores that time and its substep length in the frame data that the solve (f_81b47080) reads.
    • The instance's fixed-1/60 mode (f_81b3a964) is not touched.
    • report warns when the site isn't found once.
  • host/oot_high_fps.{h,c}:
    • oot_cloth_seconds multiplies the time by the step only for 1 < step ≤ 8. A step of 1 or less, 0, a negative step, NaN
      or Inf keeps the game's time.
    • hos_oot_cloth_seconds reads HOS_FPS_CLOTH by the repository's rule (env_value_off: unset, or anything but 0, off,
      false or no, is on). With HOS_FPS_LOG it logs an oot: cloth time line every 600 setups.
    • The header explains why.
  • docs/development.md: a row for HOS_FPS_CLOTH=0.
  • tests/test_oot_cloth_time.py (new): it fails on main.
    • f_81b3aa48's frame-data lines as lifted go through patch_file and are compiled with the host function cut from the
      real source and with gpu/vk/compat/longshot_env.h.
    • It runs frame steps 0.06 to 4.0 and the bad ones (0, −1, NaN, Inf, 8.5), instance scales 1 and 2, each setup twice from
      the same context, and HOS_FPS_CLOTH unset, 1, yes, 0 and off.
    • It checks: with a step over 1 the cloth time is the step's 60ths (else the game's 60th), over the scale; the substeps add
      up to it; the counts are the game's; the context is untouched and a second setup is the same.
  • tests/test_high_fps_fixes.py: its stand-ins include <stdlib.h> and an env_value_off, for the host file it compiles.

Measurements

Verdict: fixed at an 18 fps engine step on Windows and on the Steam Deck. The cloth's time a frame follows the engine's
step (55.6 to 66.7 ms on the PC, smoothed steps 3.33 to 4.0) instead of 16.7 ms, and in the stills the cap settles faster and
flares less, qualitatively like the 60 fps reference. The solve count is unchanged. On the Deck (handheld, about 18 fps) the
stills show the same; fps, median frame time, process CPU and GPU time show no detectable cost in these two runs per arm, and
the tail differences (p99, 1% low) are inconclusive at n=2. On the PC, 3 interleaved pairs on one build (b2d6fb15, =0
against unset, 18 fps, bench lock held, idle PC) show no measurable CPU cost: the cloth solve took a median 2.95 ms a frame
with =0 and 3.15 ms unset, and the pairs differ by −0.70, +0.01 and +0.86 ms (a median of +0.01 ms), inside the =0 runs'
own spread of 2.47–3.85 ms; the process's CPU a game frame differs by −4.21, +1.55 and −0.56 ms (medians 200.30 and 200.76 ms).
At 18 fps in Kokiri Forest (with the pause menu), Hyrule Field and Kakariko Village, and across two area changes, nothing
unstable was seen in the inspected shots.

Baseline: HOS_FPS_CLOTH=0 on this PR's build (the log and CPU rows: 5ddc9a7b). It switches off the one hook and runs the
game's own cloth path, on the same build, save and caches; there was no separate main base. The stills' before row comes from
an earlier build of this branch, 05bbcfd5, with HOS_FPS_CLOTH=0: the same unscaled path (=0 returns the game's time
unchanged in both), since the 5ddc9a7b =0 runs took no shots.

Hardware: Windows 11, RTX 5090 (NVIDIA 621.14), i7-13700K, 96 GB
Scene: Kokiri Forest beside Link's house, a child save; 2560x1440, quality preset 6 with Auto tier 5 (the game's own
upscaler: these builds have no DLSS), frame generation off,
the game's 60 cap; headless (longshot_ctl.py launch --profile test); about 18 fps from HOS_FRAME_SLEEP_MS=53
Method: the cloth's time from the log, the cloth solve's CPU share in 2 interleaved runs a side (the median), and stills:

  • A scripted route through the control bridge: 3 s idle, 2.5 s run, 3 s stop, 2.5 s run back, 3 s stop.
  • The cloth's time from the oot: cloth time lines (HOS_FPS_LOG).
  • CPU from HOS_SAMPLE_ALL and scripts/cpu_report.py (inclusive share of f_81b47080), 2 interleaved pairs, the median.
  • Stills: every present shot while the route runs (1280x720; the 60 fps reference 640x360), cropped around Link at the same
    times after the stop.
    How to reproduce: as How to reproduce; HOS_FPS_LOG=1; HOS_FPS_CLOTH=0 for the before column.
Before, HOS_FPS_CLOTH=0: this PR @ 5ddc9a7b After: this PR @ 5ddc9a7b
cloth time a frame at an 18 fps engine step (steps 3.16–4.0) 16.67 ms 55.56–66.67 ms (the step's 60ths)
cloth solve count the game's the same
cloth solve f_81b47080, % of a core (run 1 / run 2, median; a WSL session interfered: see the 3 pairs below) 7.27 / 6.31, 6.79 5.99 / 7.78, 6.88: inconclusive
game clock speed (first / second window) 0.994–0.998 / 0.929–0.943 0.996–0.998 / 0.947–0.962
Stills (cap after a stop) 60 fps reference: 05bbcfd5, HOS_FPS_CLOTH=0, 60 cap Before, HOS_FPS_CLOTH=0: 05bbcfd5, 18 fps After: this PR @ 5ddc9a7b, 18 fps
hangs down, settled by about +0.2 s tail flares out sideways at +0.2 to +0.45 s hangs down, settled by about +0.2 s

Times are the shots' present times after the stop (estimates from sampled frames, not measured settling times).

PC stills, from behind: rows 60 fps reference, Before HOS_FPS_CLOTH=0 (05bbcfd5), After this PR @ 5ddc9a7b
PC stills, toward the camera: the same rows

(5ddc9a7b, HOS_FPS_CLOTH=0, 18 fps)
oot: cloth time 16.67 ms (the game's 16.67 ms: frame step 3.333, HOS_FPS_CLOTH=0; 601 setups)
oot: cloth time 16.67 ms (the game's 16.67 ms: frame step 3.529, HOS_FPS_CLOTH=0; 1201 setups)
(5ddc9a7b, unset, 18 fps)
oot: cloth time 66.67 ms (the game's 16.67 ms: frame step 4.000; 1 setups)
oot: cloth time 58.82 ms (the game's 16.67 ms: frame step 3.529; 601 setups)
oot: cloth time 55.56 ms (the game's 16.67 ms: frame step 3.333; 1201 setups)

PC: the CPU cost, 3 interleaved pairs (after the rebase)

Build: this PR @ b2d6fb15 (on main 310e7c9d; the code of the fix is unchanged, and the PR's later rebases kept
the same cloth code), one build, HOS_FPS_CLOTH=0 against
unset. Hardware and scene as above, HOS_FRAME_SLEEP_MS=53, headless, the same save and pinned options.
Method: a route of 5 s idle, 2.5 s run, 3 s stop, 2.5 s run back, 3 s stop and 10 s idle (a 29 s window), the whole window
sampled with HOS_SAMPLE_ALL. fps and process CPU are the window's: the process's CPU time over it, divided by the bridge's
game frames. The cloth solve is scripts/cpu_report.py's inclusive share of f_81b47080, times the run's frame time.
An unsampled warm-up of each arm, then pairs in the order =0 unset, unset =0, =0 unset (17 Nov 18:54–19:01 PST).
Conditions: the bench lock held; started when both build slots were free, the PC's CPU was under 20% for 60 s and WSL under
10% of a core; WSL was at 1–8% of a core at the end of each run.

Before, HOS_FPS_CLOTH=0: this PR @ b2d6fb15 After: this PR @ b2d6fb15 After − before, by pair
fps (pair 1 / 2 / 3, median) 17.78 / 17.81 / 17.90, 17.81 17.83 / 17.91 / 17.88, 17.88 +0.05 / +0.10 / −0.02
process CPU, ms a game frame (median, range) 204.97 / 200.30 / 195.69, 200.30 (195.69–204.97) 200.76 / 201.85 / 195.13, 200.76 (195.13–201.85) −4.21 / +1.55 / −0.56, median −0.56
cloth solve f_81b47080, % of a core 6.84 / 5.25 / 4.42, 5.25 5.61 / 5.30 / 5.96, 5.61 −1.23 / +0.05 / +1.54
cloth solve, ms of CPU a frame (median, range) 3.85 / 2.95 / 2.47, 2.95 (2.47–3.85) 3.15 / 2.96 / 3.33, 3.15 (2.96–3.33) −0.70 / +0.01 / +0.86, median +0.01
cloth time a frame 16.67 ms (steps 3.16–4.0) 55.56–66.67 ms (the step's 60ths)

No measurable cost: the pairs' differences change sign, and they are smaller than the spread between runs of the same arm.
The cloth solve itself costs about 3 ms of CPU a frame at 18 fps on this PC, with or without the fix. The sampler adds to the
process CPU equally in both arms (the unsampled warm-ups: 184.65 and 179.93 ms a game frame, not counted). The fixed-1/60 mode
(f_81b3a964) is in none of the 6 samples; the frame-time setup (f_81b3aa48) is in all of them.

PC: other areas, the pause menu and area changes

Build: this PR @ b2d6fb15, =0 against unset, one run each, 18 fps, headless, every present shot while the route runs.
Route: Kokiri Forest, the pause menu opened with PLUS for about 4 s and closed, then a 2.5 s run and stop; a teleport to Hyrule
Field (an area change, with its load) and a 3 s run and a 2 s run to the right, each to a stop; a teleport to Kakariko Village,
a 3 s walk and a 2.5 s run, each to a stop.

Stills, 18 fps Before, HOS_FPS_CLOTH=0: this PR @ b2d6fb15 After: this PR @ b2d6fb15
Kakariko Village, after a walk the cap still out to the side at +0.3 to +0.45 s swings out at +0.1 to +0.2 s, behind his head from about +0.3 s
Hyrule Field, two runs (close camera, in bushes) the cap sticks up at the stop follows his head
the 30 frames after the pause menu closes at rest, no jump at rest, no jump
first shots after each area change (about 5 s after arriving) at rest at rest

In the inspected shots no jitter, explosion, stretching or clipping was seen in either arm. The log's cloth time stays 16.67 ×
the step (52.63–66.67 ms) through the pause and both loads, and has no warning beyond the 7 start-up lines of every run.
Times are estimates from the shots' present times, not measured settling times.

PC, Kakariko Village after a walk, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0), this PR @ b2d6fb15
PC, the frames after the pause menu closes, 18 fps: top After (a-f, unset), bottom Before (a-z, HOS_FPS_CLOTH=0), this PR @ b2d6fb15
PC, Hyrule Field, a run and stop, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0), this PR @ b2d6fb15

Steam Deck

Hardware: Steam Deck OLED, 16 GB (AMD Custom GPU 0932, RADV VANGOGH, Mesa 26.2.0-devel git 5c65d4fc31), SteamOS 3.9.5
(build 20261023.100), Game Mode, handheld on AC, 15 W power cap, GPU profile_peak
Build: this PR @ 5ddc9a7b, built natively for Linux (Longshot's Linux build image, tools.lock's tools, RX_MARCH=x86-64-v3;
longshot sha256 fee0f163…, longshot_vk.so c0b77984…)
Scene: Kokiri Forest, the owner's own settings (render at 100%, frame generation off), 1280x800 at 90 Hz, about 18 fps
Method: standing, 45 s windows; a warm-up of each arm, then =0, unset, unset, =0 (4 measured windows and 2 warm-ups,
all valid); frame times from the frame log, the process's CPU time per game frame (the bridge's frame counter) and GPU time a
frame from the renderer; then a scripted 30-frame run and stop with every present shot. Power-limit (FPPT) throttle flags
were set in 2-7% of the samples of the measured windows.

Before, HOS_FPS_CLOTH=0: this PR @ 5ddc9a7b After: this PR @ 5ddc9a7b
fps (run 1 / run 2, median) 18.31 / 18.17, 18.24 18.28 / 18.30, 18.29
median frame time 53.50 / 54.00, 53.75 ms 53.60 / 53.70, 53.65 ms
p99 frame time 66.4 / 91.3, 78.9 ms 64.6 / 64.9, 64.8 ms (inconclusive at n=2)
1% low 7.31 / 6.99, 7.15 fps 7.06 / 7.52, 7.29 fps
process CPU ms per bridge game frame (median) 152.6 ms 152.6 ms: no measurable CPU difference
GPU time a frame 44.06 ms 44.04 ms
cloth time a frame 16.67 ms at every step (2.14–4.00) 16.67 × the step (37.04 ms at 2.222, 52.63 at 3.158, 66.67 at 4.000)
Stills (cap after a stop, Deck) Before, HOS_FPS_CLOTH=0: this PR @ 5ddc9a7b After: this PR @ 5ddc9a7b
sticks out sideways at the stop, whips to the right by +0.2 s, still swinging at +0.45 and +0.67 s hangs behind his head from the stop, settled by +0.2 s, a slight sway after +0.45 s

No obvious stretching or clipping in the inspected frames (up to +0.67 s); these sequences are not a general stability test.
The times (+0.2 s, +0.45 s, +0.67 s) are estimates from the sampled presents' game times, not measured settling times.
Steam Deck stills: Before, HOS_FPS_CLOTH=0: this PR @ 5ddc9a7b, then After: this PR @ 5ddc9a7b

(Deck, HOS_FPS_CLOTH=0)  oot: cloth time 16.67 ms (the game's 16.67 ms: frame step 2.727, HOS_FPS_CLOTH=0; 1 setups)
(Deck, unset)            oot: cloth time 37.04 ms (the game's 16.67 ms: frame step 2.222; 1 setups)

About the first PC CPU sample (5ddc9a7b, 2 runs a side): a WSL session not part of the test started at 23:14:28 during it, and
the second =1 run shows higher worker-thread totals (69.7% against 46–51% of a core), so it showed neither a cost nor its
absence; the 3 pairs above replace it. Also tried and rejected:
multiplying the substeps by the step as well (4× at 18 fps) looked the same and took the solve from about 6% to about 26% of
a core (about +11.5 ms of CPU a frame).

Flags and settings

One new switch, to compare against the game's behaviour.

Flag What it is Before this PR After this PR Effect Helps / doesn't help / untested Recommendation
HOS_FPS_CLOTH while the engine's frame step is over 1, the cloth steps by it not there (the game's 60th) unset: on; 0, off, false, no: the game's with a step over 1 the cloth advances as far as the game; a step of 1 or less unchanged helps at an 18 fps step on Windows and on the Steam Deck; no measurable CPU cost on the PC (3 pairs) or the Deck (n=2) leave unset; 0 only to compare

Testing

Tested:

  • Game-free, after the rebase: python -I -B tests/run_all.py on b2d6fb15 (then on main 310e7c9d): 665 pass, 50 fail, 53 skipped. On main @
    310e7c9d: 663 pass, 51 fail, the same 50 and test_longshot_ctl (a 90 s timeout there; it passes here), so this PR adds no
    failure; they are listed below. tests/test_oot_cloth_time.py fails on main and passes here. Six mutants fail it (on
    5ddc9a7b): no scaling, scaling at steps of 1 or less, no upper bound, NaN let through, atoi parsing, and the default off.
    Main moved again after the runs: rebased onto 430eef4f (the fix commit only merged beside #1528's moving-floor carry in the same files, both kept; the other three commits = in git range-diff), then
    tests/test_oot_cloth_time.py passes and tests/test_floor_carry_step.py and tests/test_high_fps_fixes.py pass, and run_all.py --changed gives 42 pass, 6 fail, 2 skipped, the 6 all on main's list.
  • In the game, on Windows 11 with an RTX 5090, after the rebase: a full build of b2d6fb15 (the lift applied the site once, no
    warning); the CPU cost in 3 interleaved pairs, and the other areas, the pause menu and two area changes at 18 fps
    (Measurements).
  • In the game, on Windows 11 with an RTX 5090: a full build of 5ddc9a7b, headless, the route above at an 18 fps engine step,
    =0 and =1 (log and CPU samples, 2 pairs) and =1 with shots. The lift applied the site once
    (oot_patches: the cloth's time below 60 fps in code_024.c, no warning).
  • Linux: a native build of 5ddc9a7b (Longshot's Linux build image, tools.lock's tools, RX_MARCH=x86-64-v3) finished with the
    site applied and no warnings (longshot sha256 fee0f163…, longshot_vk.so c0b77984…).
  • Steam Deck OLED, handheld on AC: that Linux build in Kokiri Forest at about 18 fps, =0 against unset, 2 interleaved 45 s
    windows each after a warm-up, the log lines, and every present around a stop (Measurements).

Not tested:

  • The frames during a load: the shots were off during the teleports, so the first look after an area change is about 5 s
    after arriving. Other menus than the pause menu, cutscenes, combat, and adult Link.
  • Other cloth than Link's cap in close view (NPC clothes), and other areas than Kokiri Forest, Hyrule Field and Kakariko.
  • The instance's fixed-1/60 mode, which this doesn't touch: it was in none of 18 CPU samples in Kokiri Forest, and where the
    game uses it is unknown.

Must be tested: None.

Risks

What could break: while the engine's step is over 1, every character's cloth (Link's cap, NPC clothes) steps by it, with
substeps up to 4 times as long as at 60 fps (the host caps the step at 4). At 18 fps nothing unstable was seen in Kokiri
Forest (with the pause menu), Hyrule Field and Kakariko Village or across two area changes; cloth elsewhere (other areas,
NPC clothes up close, cutscenes) wasn't checked, and the same solve count doesn't prove it is stable everywhere.

Cost: none measurable. On the PC at 18 fps, in 3 interleaved pairs on one build, the cloth solve's CPU changed by −0.70,
+0.01 and +0.86 ms a frame (a median of +0.01 ms; the =0 runs alone spread over 2.47–3.85 ms), the process's CPU by −4.21,
+1.55 and −0.56 ms a game frame (a median of −0.56 ms), and fps by +0.05, +0.10 and −0.02. On the Deck, 152.6 ms of process
CPU per bridge game frame in both arms (n=2). The cloth solve itself costs about 3 ms of CPU a frame at 18 fps on this PC,
with or without the fix.

Turning it off: HOS_FPS_CLOTH=0, or revert.

Compatibility: nothing changes for saves, options, caches or the vk ABI. The lifted code changes, so the game is translated
again on update, as with any oot_patches.py change.

Issues

No issue filed; the tracker was searched (cloth, hat, Link's cap, floaty, low fps, frame step). Seen by dukenheimer on his
Steam Deck.

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. The CPU cost is measured in 3 interleaved pairs (none measurable) and stated in Risks; the other areas, the
    pause menu and area changes are in Testing.
  • 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.
  • Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
  • Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value.
  • Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md): seventeen files, one a
    run (the Deck's 4 measured windows, the PC's 5 runs of 5ddc9a7b, and 8 of b2d6fb15: the 6 timed runs and the 2 area
    runs), in their own commits; the second also corrects the first's PC settings (Auto tier 5 with the game's own upscaler,
    not DLSS). Each passes scripts/tested_configurations.py's row reader; tests/test_tested_configurations.py fails on
    main already, on a Windows line-ending case.
  • 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.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.
  • Docs updated.

The 50 checks that fail on main @ 310e7c9d and on this branch: test_auto_handheld, test_bug_report_defaults,
test_build_long_paths, test_compute_warm_apart, test_cpu_report, test_crash_dialog, test_crt_options, test_damage_debug_menu,
test_dev_packs, test_discover, test_display_startup_failure, test_dlss_feature_size, test_draw_stream_visibility,
test_failed_compile_keeps_objects, test_fsr_image_retirement, test_fsr_uniform_ownership, test_guest_imported,
test_hud_layout_row, test_import_reach, test_invalidate_quick, test_invalidate_vcore, test_job_queue, test_libc_hooks,
test_lift_lookups, test_linux_preflight, test_linux_pressure, test_mirror_budget, test_missing_nup, test_pads_after_menu,
test_parallel_init_order, test_pending_guest_import, test_pipeline_play_cache, test_present_thread, test_profiling_mode,
test_psychov35_fsr3_fg, test_readback_timeout_source, test_recorder_sync, test_replay_write_order, test_run_all_changed,
test_sdiv_overflow, test_slow_frames, test_staging_burst, test_switch_table, test_target_image_pool, test_tested_configurations,
test_upscaler_rows, test_vcore_escape, test_vk_occlusion_queries, test_walk, test_walk_key (all under tests/).

**Type:** fix · **Risk:** low · **Tested on:** Windows 11, RTX 5090; Steam Deck OLED (SteamOS, RADV) · **Needs:** none ## TL;DR Below 60 fps Link's cap floats: after he stops it swings far out and takes about a second to settle, because the game steps the cloth a 60th of a second a frame however long the frame was. This makes the cloth step as far as the rest of the game when frames are slow, so the cap settles about as at 60 fps. Checked at 18 fps on a PC and on the Steam Deck, with no measurable CPU cost and nothing unstable seen in four areas, the pause menu and two area changes. ## Breakdown - **Who it helps:** anyone below 60 fps, above all on the Steam Deck (17 to 24 fps). - **What was wrong:** the Havok cloth (Link's cap, NPC clothes) advanced 1/60 s a frame while the game advanced its frame step (3.3/60 s at 18 fps), so the cloth lagged behind Link and over-swung. - **What changes:** while the engine's frame step is over 1, the cloth's time a frame is the step's 60ths; `HOS_FPS_CLOTH=0` turns it off. - **What doesn't change:** at a step of 1 or less (60 fps and above) nothing; the solve count; the fixed-1/60 cloth mode. - **How it was checked:** a game-free test failing on main; at 18 fps on Windows (3 interleaved CPU pairs, stills in Kokiri Forest, Hyrule Field, Kakariko, the pause menu and area changes) and on the Steam Deck (2 runs a side, stills). - **Still open:** cloth above 60 fps (a separate change); other areas, cutscenes and NPC clothes up close weren't checked. - **Risk:** low: cloth steps up to 4 times as long at the lowest frame rates; no instability seen; one switch to turn it off. ## Why When the game runs below 60 fps, Link's cap floats: after he stops, it swings far out to the side and takes about a second to settle. On the Steam Deck (17 to 24 fps) players see it all the time. At 60 fps it settles in about 0.2 s. The cap is Havok cloth, and the game steps it a fixed 1/60 of a second each frame, whatever the game's own frame step for that frame. With an engine frame step of 3.3 (about 18 fps), the cloth advances 1/60 s while the rest of the game advances 3.3/60 s, about 0.3 of it. So the cloth lags behind Link: each cloth step sees his head move about 3.3 times as far, the cap swings wide, and its settling takes about 3.3 times as long in real time. On a fast PC held to 18 fps it looks the same, so the frame step alone causes it. The console would step the cloth the same way whenever its frame-rate controller drops to 30, 20 or 15 fps, so this improves on the original's behaviour at low frame rates. ## How to reproduce **Seen on:** Windows 11, RTX 5090 (NVIDIA 621.14); the Steam Deck (reported) **Settings and switches:** defaults at the game's 60 cap; `HOS_FRAME_SLEEP_MS=53` (about 18 fps) on a fast PC, or any PC or Deck that runs under 30 fps **Steps:** in Kokiri Forest, run Link forward for 2 s and let go of the stick. **Expected:** the cap follows his head and settles within about 0.2 s after he stops, as at 60 fps. **Actual:** on main, the cap's tail flares out sideways 0.2 to 0.45 s after the stop and takes about a second to settle. ## What changed While the engine's frame step is over 1, the cloth's simulate setup steps by the game's 1/60 times that step, so the cloth advances as far as the rest of the game that frame. The solve count stays the same. With a step of 1 or less nothing changes (at 60 fps and above; a 60-capped game can still have steps over 1 on slow frames, and those are scaled). The cloth above 60 fps, which still steps 1/60 a frame, is left for a separate change. - `nx2/oot_patches.py` `patch_cloth_time`: - In `f_81b3aa48`, the Havok simulate operator's per-frame setup, the load of the step context's time (+8) goes through `hos_oot_cloth_seconds` with the engine's frame step: the float `f_83b6ea90` writes at 0x84d61fc8, `60 / its frame rate`. - The setup stores that time and its substep length in the frame data that the solve (`f_81b47080`) reads. - The instance's fixed-1/60 mode (`f_81b3a964`) is not touched. - `report` warns when the site isn't found once. - `host/oot_high_fps.{h,c}`: - `oot_cloth_seconds` multiplies the time by the step only for 1 < step ≤ 8. A step of 1 or less, 0, a negative step, NaN or Inf keeps the game's time. - `hos_oot_cloth_seconds` reads `HOS_FPS_CLOTH` by the repository's rule (`env_value_off`: unset, or anything but 0, off, false or no, is on). With `HOS_FPS_LOG` it logs an `oot: cloth time` line every 600 setups. - The header explains why. - `docs/development.md`: a row for `HOS_FPS_CLOTH=0`. - `tests/test_oot_cloth_time.py` (new): it fails on main. - `f_81b3aa48`'s frame-data lines as lifted go through `patch_file` and are compiled with the host function cut from the real source and with `gpu/vk/compat/longshot_env.h`. - It runs frame steps 0.06 to 4.0 and the bad ones (0, −1, NaN, Inf, 8.5), instance scales 1 and 2, each setup twice from the same context, and `HOS_FPS_CLOTH` unset, 1, yes, 0 and off. - It checks: with a step over 1 the cloth time is the step's 60ths (else the game's 60th), over the scale; the substeps add up to it; the counts are the game's; the context is untouched and a second setup is the same. - `tests/test_high_fps_fixes.py`: its stand-ins include `<stdlib.h>` and an `env_value_off`, for the host file it compiles. ## Measurements **Verdict:** fixed at an 18 fps engine step on Windows and on the Steam Deck. The cloth's time a frame follows the engine's step (55.6 to 66.7 ms on the PC, smoothed steps 3.33 to 4.0) instead of 16.7 ms, and in the stills the cap settles faster and flares less, qualitatively like the 60 fps reference. The solve count is unchanged. On the Deck (handheld, about 18 fps) the stills show the same; fps, median frame time, process CPU and GPU time show no detectable cost in these two runs per arm, and the tail differences (p99, 1% low) are inconclusive at n=2. On the PC, 3 interleaved pairs on one build (b2d6fb15, `=0` against unset, 18 fps, bench lock held, idle PC) show no measurable CPU cost: the cloth solve took a median 2.95 ms a frame with `=0` and 3.15 ms unset, and the pairs differ by −0.70, +0.01 and +0.86 ms (a median of +0.01 ms), inside the `=0` runs' own spread of 2.47–3.85 ms; the process's CPU a game frame differs by −4.21, +1.55 and −0.56 ms (medians 200.30 and 200.76 ms). At 18 fps in Kokiri Forest (with the pause menu), Hyrule Field and Kakariko Village, and across two area changes, nothing unstable was seen in the inspected shots. Baseline: `HOS_FPS_CLOTH=0` on this PR's build (the log and CPU rows: 5ddc9a7b). It switches off the one hook and runs the game's own cloth path, on the same build, save and caches; there was no separate main base. The stills' before row comes from an earlier build of this branch, 05bbcfd5, with `HOS_FPS_CLOTH=0`: the same unscaled path (`=0` returns the game's time unchanged in both), since the 5ddc9a7b `=0` runs took no shots. Hardware: Windows 11, RTX 5090 (NVIDIA 621.14), i7-13700K, 96 GB Scene: Kokiri Forest beside Link's house, a child save; 2560x1440, quality preset 6 with Auto tier 5 (the game's own upscaler: these builds have no DLSS), frame generation off, the game's 60 cap; headless (`longshot_ctl.py launch --profile test`); about 18 fps from `HOS_FRAME_SLEEP_MS=53` Method: the cloth's time from the log, the cloth solve's CPU share in 2 interleaved runs a side (the median), and stills: - A scripted route through the control bridge: 3 s idle, 2.5 s run, 3 s stop, 2.5 s run back, 3 s stop. - The cloth's time from the `oot: cloth time` lines (`HOS_FPS_LOG`). - CPU from `HOS_SAMPLE_ALL` and `scripts/cpu_report.py` (inclusive share of `f_81b47080`), 2 interleaved pairs, the median. - Stills: every present shot while the route runs (1280x720; the 60 fps reference 640x360), cropped around Link at the same times after the stop. How to reproduce: as How to reproduce; `HOS_FPS_LOG=1`; `HOS_FPS_CLOTH=0` for the before column. | | Before, `HOS_FPS_CLOTH=0`: this PR @ 5ddc9a7b | After: this PR @ 5ddc9a7b | |---|---|---| | cloth time a frame at an 18 fps engine step (steps 3.16–4.0) | 16.67 ms | 55.56–66.67 ms (the step's 60ths) | | cloth solve count | the game's | the same | | cloth solve `f_81b47080`, % of a core (run 1 / run 2, median; a WSL session interfered: see the 3 pairs below) | 7.27 / 6.31, 6.79 | 5.99 / 7.78, 6.88: inconclusive | | game clock speed (first / second window) | 0.994–0.998 / 0.929–0.943 | 0.996–0.998 / 0.947–0.962 | | Stills (cap after a stop) | 60 fps reference: 05bbcfd5, `HOS_FPS_CLOTH=0`, 60 cap | Before, `HOS_FPS_CLOTH=0`: 05bbcfd5, 18 fps | After: this PR @ 5ddc9a7b, 18 fps | |---|---|---|---| | | hangs down, settled by about +0.2 s | tail flares out sideways at +0.2 to +0.45 s | hangs down, settled by about +0.2 s | Times are the shots' present times after the stop (estimates from sampled frames, not measured settling times). ![PC stills, from behind: rows 60 fps reference, Before HOS_FPS_CLOTH=0 (05bbcfd5), After this PR @ 5ddc9a7b](https://git.magicbean.dev/attachments/82916318-6f90-47e6-85b5-1b9b10dc64a9) ![PC stills, toward the camera: the same rows](https://git.magicbean.dev/attachments/d9a78c48-6797-4aae-a7de-cf936feee6e1) ``` (5ddc9a7b, HOS_FPS_CLOTH=0, 18 fps) oot: cloth time 16.67 ms (the game's 16.67 ms: frame step 3.333, HOS_FPS_CLOTH=0; 601 setups) oot: cloth time 16.67 ms (the game's 16.67 ms: frame step 3.529, HOS_FPS_CLOTH=0; 1201 setups) (5ddc9a7b, unset, 18 fps) oot: cloth time 66.67 ms (the game's 16.67 ms: frame step 4.000; 1 setups) oot: cloth time 58.82 ms (the game's 16.67 ms: frame step 3.529; 601 setups) oot: cloth time 55.56 ms (the game's 16.67 ms: frame step 3.333; 1201 setups) ``` #### PC: the CPU cost, 3 interleaved pairs (after the rebase) Build: this PR @ b2d6fb15 (on main 310e7c9d; the code of the fix is unchanged, and the PR's later rebases kept the same cloth code), one build, `HOS_FPS_CLOTH=0` against unset. Hardware and scene as above, `HOS_FRAME_SLEEP_MS=53`, headless, the same save and pinned options. Method: a route of 5 s idle, 2.5 s run, 3 s stop, 2.5 s run back, 3 s stop and 10 s idle (a 29 s window), the whole window sampled with `HOS_SAMPLE_ALL`. fps and process CPU are the window's: the process's CPU time over it, divided by the bridge's game frames. The cloth solve is `scripts/cpu_report.py`'s inclusive share of `f_81b47080`, times the run's frame time. An unsampled warm-up of each arm, then pairs in the order `=0` unset, unset `=0`, `=0` unset (17 Nov 18:54–19:01 PST). Conditions: the bench lock held; started when both build slots were free, the PC's CPU was under 20% for 60 s and WSL under 10% of a core; WSL was at 1–8% of a core at the end of each run. | | Before, `HOS_FPS_CLOTH=0`: this PR @ b2d6fb15 | After: this PR @ b2d6fb15 | After − before, by pair | |---|---|---|---| | fps (pair 1 / 2 / 3, median) | 17.78 / 17.81 / 17.90, 17.81 | 17.83 / 17.91 / 17.88, 17.88 | +0.05 / +0.10 / −0.02 | | process CPU, ms a game frame (median, range) | 204.97 / 200.30 / 195.69, 200.30 (195.69–204.97) | 200.76 / 201.85 / 195.13, 200.76 (195.13–201.85) | −4.21 / +1.55 / −0.56, median −0.56 | | cloth solve `f_81b47080`, % of a core | 6.84 / 5.25 / 4.42, 5.25 | 5.61 / 5.30 / 5.96, 5.61 | −1.23 / +0.05 / +1.54 | | cloth solve, ms of CPU a frame (median, range) | 3.85 / 2.95 / 2.47, 2.95 (2.47–3.85) | 3.15 / 2.96 / 3.33, 3.15 (2.96–3.33) | −0.70 / +0.01 / +0.86, median +0.01 | | cloth time a frame | 16.67 ms (steps 3.16–4.0) | 55.56–66.67 ms (the step's 60ths) | | No measurable cost: the pairs' differences change sign, and they are smaller than the spread between runs of the same arm. The cloth solve itself costs about 3 ms of CPU a frame at 18 fps on this PC, with or without the fix. The sampler adds to the process CPU equally in both arms (the unsampled warm-ups: 184.65 and 179.93 ms a game frame, not counted). The fixed-1/60 mode (`f_81b3a964`) is in none of the 6 samples; the frame-time setup (`f_81b3aa48`) is in all of them. #### PC: other areas, the pause menu and area changes Build: this PR @ b2d6fb15, `=0` against unset, one run each, 18 fps, headless, every present shot while the route runs. Route: Kokiri Forest, the pause menu opened with PLUS for about 4 s and closed, then a 2.5 s run and stop; a teleport to Hyrule Field (an area change, with its load) and a 3 s run and a 2 s run to the right, each to a stop; a teleport to Kakariko Village, a 3 s walk and a 2.5 s run, each to a stop. | Stills, 18 fps | Before, `HOS_FPS_CLOTH=0`: this PR @ b2d6fb15 | After: this PR @ b2d6fb15 | |---|---|---| | Kakariko Village, after a walk | the cap still out to the side at +0.3 to +0.45 s | swings out at +0.1 to +0.2 s, behind his head from about +0.3 s | | Hyrule Field, two runs (close camera, in bushes) | the cap sticks up at the stop | follows his head | | the 30 frames after the pause menu closes | at rest, no jump | at rest, no jump | | first shots after each area change (about 5 s after arriving) | at rest | at rest | In the inspected shots no jitter, explosion, stretching or clipping was seen in either arm. The log's cloth time stays 16.67 × the step (52.63–66.67 ms) through the pause and both loads, and has no warning beyond the 7 start-up lines of every run. Times are estimates from the shots' present times, not measured settling times. ![PC, Kakariko Village after a walk, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0), this PR @ b2d6fb15](https://git.magicbean.dev/attachments/d1e800cb-5529-46f4-bb6d-5a6949029c53) ![PC, the frames after the pause menu closes, 18 fps: top After (a-f, unset), bottom Before (a-z, HOS_FPS_CLOTH=0), this PR @ b2d6fb15](https://git.magicbean.dev/attachments/5f8517f1-6df5-4ea9-bf8b-124b37494862) ![PC, Hyrule Field, a run and stop, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0), this PR @ b2d6fb15](https://git.magicbean.dev/attachments/2e687024-deb4-4016-90c9-c8d0f8a3d12c) #### Steam Deck Hardware: Steam Deck OLED, 16 GB (AMD Custom GPU 0932, RADV VANGOGH, Mesa 26.2.0-devel git 5c65d4fc31), SteamOS 3.9.5 (build 20261023.100), Game Mode, handheld on AC, 15 W power cap, GPU profile_peak Build: this PR @ 5ddc9a7b, built natively for Linux (Longshot's Linux build image, tools.lock's tools, `RX_MARCH=x86-64-v3`; `longshot` sha256 fee0f163…, `longshot_vk.so` c0b77984…) Scene: Kokiri Forest, the owner's own settings (render at 100%, frame generation off), 1280x800 at 90 Hz, about 18 fps Method: standing, 45 s windows; a warm-up of each arm, then `=0`, unset, unset, `=0` (4 measured windows and 2 warm-ups, all valid); frame times from the frame log, the process's CPU time per game frame (the bridge's frame counter) and GPU time a frame from the renderer; then a scripted 30-frame run and stop with every present shot. Power-limit (FPPT) throttle flags were set in 2-7% of the samples of the measured windows. | | Before, `HOS_FPS_CLOTH=0`: this PR @ 5ddc9a7b | After: this PR @ 5ddc9a7b | |---|---|---| | fps (run 1 / run 2, median) | 18.31 / 18.17, 18.24 | 18.28 / 18.30, 18.29 | | median frame time | 53.50 / 54.00, 53.75 ms | 53.60 / 53.70, 53.65 ms | | p99 frame time | 66.4 / 91.3, 78.9 ms | 64.6 / 64.9, 64.8 ms (inconclusive at n=2) | | 1% low | 7.31 / 6.99, 7.15 fps | 7.06 / 7.52, 7.29 fps | | process CPU ms per bridge game frame (median) | 152.6 ms | 152.6 ms: no measurable CPU difference | | GPU time a frame | 44.06 ms | 44.04 ms | | cloth time a frame | 16.67 ms at every step (2.14–4.00) | 16.67 × the step (37.04 ms at 2.222, 52.63 at 3.158, 66.67 at 4.000) | | Stills (cap after a stop, Deck) | Before, `HOS_FPS_CLOTH=0`: this PR @ 5ddc9a7b | After: this PR @ 5ddc9a7b | |---|---|---| | | sticks out sideways at the stop, whips to the right by +0.2 s, still swinging at +0.45 and +0.67 s | hangs behind his head from the stop, settled by +0.2 s, a slight sway after +0.45 s | No obvious stretching or clipping in the inspected frames (up to +0.67 s); these sequences are not a general stability test. The times (+0.2 s, +0.45 s, +0.67 s) are estimates from the sampled presents' game times, not measured settling times. ![Steam Deck stills: Before, HOS_FPS_CLOTH=0: this PR @ 5ddc9a7b, then After: this PR @ 5ddc9a7b](https://git.magicbean.dev/attachments/b21eafba-e56e-4ad0-ad00-9d06a1643e62) ``` (Deck, HOS_FPS_CLOTH=0) oot: cloth time 16.67 ms (the game's 16.67 ms: frame step 2.727, HOS_FPS_CLOTH=0; 1 setups) (Deck, unset) oot: cloth time 37.04 ms (the game's 16.67 ms: frame step 2.222; 1 setups) ``` About the first PC CPU sample (5ddc9a7b, 2 runs a side): a WSL session not part of the test started at 23:14:28 during it, and the second `=1` run shows higher worker-thread totals (69.7% against 46–51% of a core), so it showed neither a cost nor its absence; the 3 pairs above replace it. Also tried and rejected: multiplying the substeps by the step as well (4× at 18 fps) looked the same and took the solve from about 6% to about 26% of a core (about +11.5 ms of CPU a frame). ### Flags and settings One new switch, to compare against the game's behaviour. | Flag | What it is | Before this PR | After this PR | Effect | Helps / doesn't help / untested | Recommendation | |---|---|---|---|---|---|---| | `HOS_FPS_CLOTH` | while the engine's frame step is over 1, the cloth steps by it | not there (the game's 60th) | unset: on; `0`, `off`, `false`, `no`: the game's | with a step over 1 the cloth advances as far as the game; a step of 1 or less unchanged | helps at an 18 fps step on Windows and on the Steam Deck; no measurable CPU cost on the PC (3 pairs) or the Deck (n=2) | leave unset; `0` only to compare | ## Testing **Tested:** - Game-free, after the rebase: `python -I -B tests/run_all.py` on b2d6fb15 (then on main 310e7c9d): 665 pass, 50 fail, 53 skipped. On main @ 310e7c9d: 663 pass, 51 fail, the same 50 and `test_longshot_ctl` (a 90 s timeout there; it passes here), so this PR adds no failure; they are listed below. `tests/test_oot_cloth_time.py` fails on main and passes here. Six mutants fail it (on 5ddc9a7b): no scaling, scaling at steps of 1 or less, no upper bound, NaN let through, `atoi` parsing, and the default off. Main moved again after the runs: rebased onto 430eef4f (the fix commit only merged beside #1528's moving-floor carry in the same files, both kept; the other three commits `=` in `git range-diff`), then `tests/test_oot_cloth_time.py` passes and `tests/test_floor_carry_step.py` and `tests/test_high_fps_fixes.py` pass, and `run_all.py --changed` gives 42 pass, 6 fail, 2 skipped, the 6 all on main's list. - In the game, on Windows 11 with an RTX 5090, after the rebase: a full build of b2d6fb15 (the lift applied the site once, no warning); the CPU cost in 3 interleaved pairs, and the other areas, the pause menu and two area changes at 18 fps (Measurements). - In the game, on Windows 11 with an RTX 5090: a full build of 5ddc9a7b, headless, the route above at an 18 fps engine step, `=0` and `=1` (log and CPU samples, 2 pairs) and `=1` with shots. The lift applied the site once (`oot_patches: the cloth's time below 60 fps in code_024.c`, no warning). - Linux: a native build of 5ddc9a7b (Longshot's Linux build image, tools.lock's tools, `RX_MARCH=x86-64-v3`) finished with the site applied and no warnings (`longshot` sha256 fee0f163…, `longshot_vk.so` c0b77984…). - Steam Deck OLED, handheld on AC: that Linux build in Kokiri Forest at about 18 fps, `=0` against unset, 2 interleaved 45 s windows each after a warm-up, the log lines, and every present around a stop (Measurements). **Not tested:** - The frames during a load: the shots were off during the teleports, so the first look after an area change is about 5 s after arriving. Other menus than the pause menu, cutscenes, combat, and adult Link. - Other cloth than Link's cap in close view (NPC clothes), and other areas than Kokiri Forest, Hyrule Field and Kakariko. - The instance's fixed-1/60 mode, which this doesn't touch: it was in none of 18 CPU samples in Kokiri Forest, and where the game uses it is unknown. **Must be tested:** None. ## Risks **What could break:** while the engine's step is over 1, every character's cloth (Link's cap, NPC clothes) steps by it, with substeps up to 4 times as long as at 60 fps (the host caps the step at 4). At 18 fps nothing unstable was seen in Kokiri Forest (with the pause menu), Hyrule Field and Kakariko Village or across two area changes; cloth elsewhere (other areas, NPC clothes up close, cutscenes) wasn't checked, and the same solve count doesn't prove it is stable everywhere. **Cost:** none measurable. On the PC at 18 fps, in 3 interleaved pairs on one build, the cloth solve's CPU changed by −0.70, +0.01 and +0.86 ms a frame (a median of +0.01 ms; the `=0` runs alone spread over 2.47–3.85 ms), the process's CPU by −4.21, +1.55 and −0.56 ms a game frame (a median of −0.56 ms), and fps by +0.05, +0.10 and −0.02. On the Deck, 152.6 ms of process CPU per bridge game frame in both arms (n=2). The cloth solve itself costs about 3 ms of CPU a frame at 18 fps on this PC, with or without the fix. **Turning it off:** `HOS_FPS_CLOTH=0`, or revert. **Compatibility:** nothing changes for saves, options, caches or the vk ABI. The lifted code changes, so the game is translated again on update, as with any `oot_patches.py` change. ## Issues No issue filed; the tracker was searched (cloth, hat, Link's cap, floaty, low fps, frame step). Seen by dukenheimer on his Steam Deck. ## 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. The CPU cost is measured in 3 interleaved pairs (none measurable) and stated in Risks; the other areas, the pause menu and area changes are in Testing. - [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] Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [x] Switches documented (docs/development.md; the README for a menu row) and shipped at their recommended value. - [x] Screenshots of the same spot, captioned like the Measurements columns, for a change that shows on screen. - [x] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`): seventeen files, one a run (the Deck's 4 measured windows, the PC's 5 runs of 5ddc9a7b, and 8 of b2d6fb15: the 6 timed runs and the 2 area runs), in their own commits; the second also corrects the first's PC settings (Auto tier 5 with the game's own upscaler, not DLSS). Each passes `scripts/tested_configurations.py`'s row reader; `tests/test_tested_configurations.py` fails on main already, on a Windows line-ending case. - [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. - [x] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. - [x] Docs updated. The 50 checks that fail on main @ 310e7c9d and on this branch: test_auto_handheld, test_bug_report_defaults, test_build_long_paths, test_compute_warm_apart, test_cpu_report, test_crash_dialog, test_crt_options, test_damage_debug_menu, test_dev_packs, test_discover, test_display_startup_failure, test_dlss_feature_size, test_draw_stream_visibility, test_failed_compile_keeps_objects, test_fsr_image_retirement, test_fsr_uniform_ownership, test_guest_imported, test_hud_layout_row, test_import_reach, test_invalidate_quick, test_invalidate_vcore, test_job_queue, test_libc_hooks, test_lift_lookups, test_linux_preflight, test_linux_pressure, test_mirror_budget, test_missing_nup, test_pads_after_menu, test_parallel_init_order, test_pending_guest_import, test_pipeline_play_cache, test_present_thread, test_profiling_mode, test_psychov35_fsr3_fg, test_readback_timeout_source, test_recorder_sync, test_replay_write_order, test_run_all_changed, test_sdiv_overflow, test_slow_frames, test_staging_burst, test_switch_table, test_target_image_pool, test_tested_configurations, test_upscaler_rows, test_vcore_escape, test_vk_occlusion_queries, test_walk, test_walk_key (all under tests/).
Assisted-by: GitHub Copilot (Claude Opus 5.5)
Co-authored-by: Copilot App <[email protected]>
f_81b3aa48 takes the cloth's time from its step context, a 60th of a second whatever the frame (16.67 ms measured at 18 fps, ~45 setups a frame at 18 and 60 fps), so below 60 fps the cloth ran at fps/60 of the clock: Link's cap swung out and settled slowly. While the game's frame step (f_83b6ea90's float at 0x84d61fc8) is over 1, hos_oot_cloth_seconds multiplies that time by it: the same solves, the cloth on the clock. 60 fps and above unchanged. HOS_FPS_CLOTH=0 keeps the game's.

Assisted-by: GitHub Copilot (Claude Opus 5.5)
Co-authored-by: Copilot App <[email protected]>
docs(tested): the hat cloth fix's runs on the PC and the Steam Deck, one record a run
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Failing after 9s
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
Website / Website on Cloudflare (pull_request) Has been cancelled
e8a8137f10
Assisted-by: GitHub Copilot (Claude Opus 5.5)
Co-authored-by: Copilot App <[email protected]>
Author
Contributor

Tested in game: Windows 11, RTX 5090 (NVIDIA 621.14): a full build of 5ddc9a7b, headless, Kokiri Forest at about 18 fps (HOS_FRAME_SLEEP_MS=53), HOS_FPS_CLOTH=0 against unset: the oot: cloth time line follows the engine step (55.6-66.7 ms against 16.67 ms) and Link's cap settles by about +0.2 s after a stop instead of flaring out. Steam Deck OLED (SteamOS 3.9.5, RADV, handheld on AC): a native Linux build of 5ddc9a7b, Kokiri Forest at about 18 fps, the same A/B: the same in the stills and the log, with fps, median frame time, process CPU and GPU time unchanged within 2 runs per arm.

Tested in game: Windows 11, RTX 5090 (NVIDIA 621.14): a full build of 5ddc9a7b, headless, Kokiri Forest at about 18 fps (HOS_FRAME_SLEEP_MS=53), HOS_FPS_CLOTH=0 against unset: the oot: cloth time line follows the engine step (55.6-66.7 ms against 16.67 ms) and Link's cap settles by about +0.2 s after a stop instead of flaring out. Steam Deck OLED (SteamOS 3.9.5, RADV, handheld on AC): a native Linux build of 5ddc9a7b, Kokiri Forest at about 18 fps, the same A/B: the same in the stills and the log, with fps, median frame time, process CPU and GPU time unchanged within 2 runs per arm.
Author
Contributor

The stills (Link's cap around a stop, crops of shots taken every present; times are the shots' present times after the stop, estimates from sampled frames).

PC, Windows 11, RTX 5090. Rows: the 60 fps reference (05bbcfd5, HOS_FPS_CLOTH=0, 60 cap); Before, HOS_FPS_CLOTH=0: 05bbcfd5, 18 fps (the same unscaled path; the 5ddc9a7b =0 runs took no shots); After: this PR @ 5ddc9a7b, 18 fps.

PC, from behind
PC, toward the camera

Steam Deck OLED, handheld on AC, about 18 fps. Rows: Before, HOS_FPS_CLOTH=0: this PR @ 5ddc9a7b; After: this PR @ 5ddc9a7b.

Steam Deck

The stills (Link's cap around a stop, crops of shots taken every present; times are the shots' present times after the stop, estimates from sampled frames). PC, Windows 11, RTX 5090. Rows: the 60 fps reference (05bbcfd5, `HOS_FPS_CLOTH=0`, 60 cap); Before, `HOS_FPS_CLOTH=0`: 05bbcfd5, 18 fps (the same unscaled path; the 5ddc9a7b `=0` runs took no shots); After: this PR @ 5ddc9a7b, 18 fps. ![PC, from behind](https://git.magicbean.dev/attachments/82916318-6f90-47e6-85b5-1b9b10dc64a9) ![PC, toward the camera](https://git.magicbean.dev/attachments/d9a78c48-6797-4aae-a7de-cf936feee6e1) Steam Deck OLED, handheld on AC, about 18 fps. Rows: Before, `HOS_FPS_CLOTH=0`: this PR @ 5ddc9a7b; After: this PR @ 5ddc9a7b. ![Steam Deck](https://git.magicbean.dev/attachments/b21eafba-e56e-4ad0-ad00-9d06a1643e62)
dukenheimer changed title from WIP: fix(fps): Link's cap and other cloth keep the game's clock below 60 fps to fix(fps): Link's cap and other cloth keep the game's clock below 60 fps 2026-11-17 09:28:46 +00:00
TrashPanda approved these changes 2026-11-17 10:11:59 +00:00
Dismissed
TrashPanda left a comment

Below 60 fps the cloth steps as far as the rest of the game that frame, and the number of solves stays the same. I read head e8a8137f. It applies onto current main. This can merge as it is.

f_81b3aa48 loads the step context's time and, while the engine's frame step is over 1 and at most 8, multiplies that time by the step. A step of 1 or less, 0, a negative step, NaN or Inf keeps the game's 60th. HOS_FPS_CLOTH=0 (also off, false or no) does the same. The fixed 1/60 mode is not patched. The site has to be found once, or the lift warns and leaves it. The game-free test runs the patched frame-data lines: the substeps add up to the scaled time, the counts stay the game's, and a second setup from the same context matches. The played code is 5ddc9a7b; the tip only adds the measured rows, one file each. On that build, at about 18 fps, the cloth's time follows the step on Windows and on the Steam Deck, and the cap settles instead of flaring out. Above 60 fps the cloth is unchanged.

Below 60 fps the cloth steps as far as the rest of the game that frame, and the number of solves stays the same. I read head `e8a8137f`. It applies onto current main. This can merge as it is. `f_81b3aa48` loads the step context's time and, while the engine's frame step is over 1 and at most 8, multiplies that time by the step. A step of 1 or less, 0, a negative step, NaN or Inf keeps the game's 60th. `HOS_FPS_CLOTH=0` (also off, false or no) does the same. The fixed 1/60 mode is not patched. The site has to be found once, or the lift warns and leaves it. The game-free test runs the patched frame-data lines: the substeps add up to the scaled time, the counts stay the game's, and a second setup from the same context matches. The played code is `5ddc9a7b`; the tip only adds the measured rows, one file each. On that build, at about 18 fps, the cloth's time follows the step on Windows and on the Steam Deck, and the cap settles instead of flaring out. Above 60 fps the cloth is unchanged.
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: the author's own in-game runs on Windows 11 with an RTX 5090 and on a Steam Deck OLED.
  • Nothing gets worse that I know of: not ticked: Testing says the PC's CPU cost of the cloth fix is inconclusive and cloth stability in other areas was not checked. Measure that cost and state it in Risks, then tick it.
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: the author's own in-game runs on Windows 11 with an RTX 5090 and on a Steam Deck OLED. - *Nothing gets worse that I know of*: not ticked: Testing says the PC's CPU cost of the cloth fix is inconclusive and cloth stability in other areas was not checked. Measure that cost and state it in Risks, then tick it.
dukenheimer force-pushed fix/hat-cloth-low-fps from e8a8137f10
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Failing after 9s
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
Website / Website on Cloudflare (pull_request) Has been cancelled
to a11839b55a
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 5s
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
Website / Website on Cloudflare (pull_request) Has been cancelled
2026-11-18 03:15:19 +00:00
Compare
dukenheimer dismissed TrashPanda's review 2026-11-18 03:15:19 +00:00
Reason:

New commits pushed, approval review dismissed automatically according to repository settings

Author
Contributor

@HumanBean thanks: measured and checked, and the box is ticked now (details in Measurements, Testing and Risks).

  • CPU cost: one build (b2d6fb15), HOS_FPS_CLOTH=0 against unset, 18 fps, headless, 3 interleaved pairs with the bench lock held on an idle PC. The cloth solve took a median of 2.95 ms of CPU a frame with =0 and 3.15 ms unset; by pair the change was −0.70, +0.01 and +0.86 ms (a median of +0.01 ms), inside the =0 runs' own spread of 2.47–3.85 ms. Process CPU per game frame: medians 200.30 and 200.76 ms (pairs −4.21, +1.55, −0.56); fps 17.81 and 17.88. So no measurable cost; it's in Risks.
  • Other areas at 18 fps: Kokiri Forest with the pause menu opened and closed, a teleport to Hyrule Field (two runs to a stop), a teleport to Kakariko Village (a walk and a run to a stop), each arm once with every present shot. No jitter, explosion, stretching or clipping in the inspected shots, including the 30 frames after the menu closes; with the fix the cap settles faster, as in Kokiri.
  • Fixed-1/60 mode: not touched by this PR; it appeared in none of the 6 new CPU samples (nor the 12 earlier ones).
  • Not checked: the frames during a load (shots were off for the teleports), cutscenes, NPC clothes up close, other areas.

Also rebased onto main ef6038ab (same patches), and the older PC records' "DLSS" is corrected: these builds have none, Auto chose tier 5 with the game's own upscaler.

Kakariko Village after a walk, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0), this PR @ b2d6fb15
The frames after the pause menu closes, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0)
Hyrule Field, a run and stop, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0)

@HumanBean thanks: measured and checked, and the box is ticked now (details in Measurements, Testing and Risks). - **CPU cost:** one build (b2d6fb15), `HOS_FPS_CLOTH=0` against unset, 18 fps, headless, 3 interleaved pairs with the bench lock held on an idle PC. The cloth solve took a median of 2.95 ms of CPU a frame with `=0` and 3.15 ms unset; by pair the change was −0.70, +0.01 and +0.86 ms (a median of +0.01 ms), inside the `=0` runs' own spread of 2.47–3.85 ms. Process CPU per game frame: medians 200.30 and 200.76 ms (pairs −4.21, +1.55, −0.56); fps 17.81 and 17.88. So no measurable cost; it's in Risks. - **Other areas at 18 fps:** Kokiri Forest with the pause menu opened and closed, a teleport to Hyrule Field (two runs to a stop), a teleport to Kakariko Village (a walk and a run to a stop), each arm once with every present shot. No jitter, explosion, stretching or clipping in the inspected shots, including the 30 frames after the menu closes; with the fix the cap settles faster, as in Kokiri. - **Fixed-1/60 mode:** not touched by this PR; it appeared in none of the 6 new CPU samples (nor the 12 earlier ones). - **Not checked:** the frames during a load (shots were off for the teleports), cutscenes, NPC clothes up close, other areas. Also rebased onto main ef6038ab (same patches), and the older PC records' "DLSS" is corrected: these builds have none, Auto chose tier 5 with the game's own upscaler. ![Kakariko Village after a walk, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0), this PR @ b2d6fb15](https://git.magicbean.dev/attachments/d1e800cb-5529-46f4-bb6d-5a6949029c53) ![The frames after the pause menu closes, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0)](https://git.magicbean.dev/attachments/5f8517f1-6df5-4ea9-bf8b-124b37494862) ![Hyrule Field, a run and stop, 18 fps: top After (unset), bottom Before (HOS_FPS_CLOTH=0)](https://git.magicbean.dev/attachments/2e687024-deb4-4016-90c9-c8d0f8a3d12c)
Contributor

@dukenheimer: #1485 turned out to be Havok cloth above a 60 cap: near King Zora the cloth solve (f_81b47080) takes ~10.5 ms of CPU a frame against ~2 a few rooms away, and holds the frame at ~55 fps with a 240 cap (numbers: #1485 (comment)). This PR leaves cloth above 60 fps open: is it on your list? If not, we'd like to claim solving the cloth at most 60 times a second above a 60 cap, built on top of this PR's patch_cloth_time so the two don't collide.

@dukenheimer: #1485 turned out to be Havok cloth above a 60 cap: near King Zora the cloth solve (`f_81b47080`) takes ~10.5 ms of CPU a frame against ~2 a few rooms away, and holds the frame at ~55 fps with a 240 cap (numbers: https://git.magicbean.dev/MagicBeanDev/Longshot/issues/1485#issuecomment-48924). This PR leaves cloth above 60 fps open: is it on your list? If not, we'd like to claim solving the cloth at most 60 times a second above a 60 cap, built on top of this PR's `patch_cloth_time` so the two don't collide.
dukenheimer force-pushed fix/hat-cloth-low-fps from a11839b55a
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 5s
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
Website / Website on Cloudflare (pull_request) Has been cancelled
to e418c77a6e
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 5s
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
Website / Website on Cloudflare (pull_request) Has been cancelled
2026-11-18 14:45:32 +00:00
Compare
Author
Contributor

Rebased onto main 430eef4f (head e418c77a) for @TrashPanda's approval: no change in behaviour. The only conflicts were #1528's moving-floor carry landing beside the cloth fix in host/oot_high_fps.{h,c} and nx2/oot_patches.py (its function, header paragraph, patch function and report warning sit next to the cloth's); both kept as they were, nothing of either edited beyond the shared file comment naming both. The test and both docs commits are unchanged (range-diff =). tests/test_oot_cloth_time.py, test_floor_carry_step.py and test_high_fps_fixes.py pass; run_all.py --changed: 42 pass, 6 fail, all failing on main too.

Rebased onto main 430eef4f (head e418c77a) for @TrashPanda's approval: no change in behaviour. The only conflicts were #1528's moving-floor carry landing beside the cloth fix in host/oot_high_fps.{h,c} and nx2/oot_patches.py (its function, header paragraph, patch function and report warning sit next to the cloth's); both kept as they were, nothing of either edited beyond the shared file comment naming both. The test and both docs commits are unchanged (range-diff =). tests/test_oot_cloth_time.py, test_floor_carry_step.py and test_high_fps_fixes.py pass; run_all.py --changed: 42 pass, 6 fail, all failing on main too.
Author
Contributor

@enum Not on our list. #1384 deliberately leaves cloth above a 60 cap as it is: its scope is a step of more than one, below 60 fps. Please go ahead and claim stepping it at most 60 times a second above a 60 cap. Building on patch_cloth_time sounds right to us.

Two things from our side that may help:

  • #1384's tests (test_oot_cloth_time) pin the below-60 behaviour, so a change above 60 should leave those passing as they are.
  • The rebased head is e418c77a, on main 430eef4f.

If you'd like a Steam Deck run of it once it's up, ask.

@enum Not on our list. #1384 deliberately leaves cloth above a 60 cap as it is: its scope is a step of more than one, below 60 fps. Please go ahead and claim stepping it at most 60 times a second above a 60 cap. Building on `patch_cloth_time` sounds right to us. Two things from our side that may help: - #1384's tests (`test_oot_cloth_time`) pin the below-60 behaviour, so a change above 60 should leave those passing as they are. - The rebased head is `e418c77a`, on main `430eef4f`. If you'd like a Steam Deck run of it once it's up, ask.
Contributor

@dukenheimer: thanks for the go-ahead; it's up as #1628 (stacked on this PR's e418c77a, the last three commits are mine). One thing for this PR: tests/test_switch_table.py says HOS_FPS_CLOTH is read (host/oot_high_fps.c:147) and has no row in gpu/vk/switches.def. #1628 adds HOS_FPS_CLOTH_60's row right before HOS_FPS_LOG; HOS_FPS_CLOTH's would go just above it. Also, if the Steam Deck run you offered is still on: HOS_FPS_CLOTH_60=1 at a cap above 60 in Zora's Domain (child) is the case to look at.

@dukenheimer: thanks for the go-ahead; it's up as #1628 (stacked on this PR's `e418c77a`, the last three commits are mine). One thing for this PR: `tests/test_switch_table.py` says `HOS_FPS_CLOTH is read (host/oot_high_fps.c:147) and has no row in gpu/vk/switches.def`. #1628 adds `HOS_FPS_CLOTH_60`'s row right before `HOS_FPS_LOG`; `HOS_FPS_CLOTH`'s would go just above it. Also, if the Steam Deck run you offered is still on: `HOS_FPS_CLOTH_60=1` at a cap above 60 in Zora's Domain (child) is the case to look at.
dukenheimer force-pushed fix/hat-cloth-low-fps from e418c77a6e
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 5s
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
Website / Website on Cloudflare (pull_request) Has been cancelled
to dc01d2b798
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 4s
2026-11-18 18:06:01 +00:00
Compare
Author
Contributor

@enum thanks, fixed: HOS_FPS_CLOTH now has its row in gpu/vk/switches.def, just above HOS_FPS_LOG (kind kill, like HOS_FPS_MOVIE and HOS_FPS_STEP). Head dc01d2b7, rebased on main c507b98c. test_switch_table no longer names it; it still fails on the same 8 switches as main. test_oot_cloth_time passes. #1628's HOS_FPS_CLOTH_60 row would go between it and HOS_FPS_LOG.

The Steam Deck run of #1628 is queued after our current Deck blocks. The Deck runs below 60 in Zora's Domain, so what it can show is no crash, the picture against main's, and the "oot: cloth solved" line, not an fps change.

@enum thanks, fixed: `HOS_FPS_CLOTH` now has its row in `gpu/vk/switches.def`, just above `HOS_FPS_LOG` (kind `kill`, like `HOS_FPS_MOVIE` and `HOS_FPS_STEP`). Head `dc01d2b7`, rebased on main `c507b98c`. `test_switch_table` no longer names it; it still fails on the same 8 switches as main. `test_oot_cloth_time` passes. #1628's `HOS_FPS_CLOTH_60` row would go between it and `HOS_FPS_LOG`. The Steam Deck run of #1628 is queued after our current Deck blocks. The Deck runs below 60 in Zora's Domain, so what it can show is no crash, the picture against main's, and the "oot: cloth solved" line, not an fps change.
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 4s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
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/hat-cloth-low-fps:dukenheimer-fix/hat-cloth-low-fps'
git switch 'dukenheimer-fix/hat-cloth-low-fps'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
4 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!1384
No description provided.