MagicBeanDev/Longshot
MagicBeanDev/Longshot
Watch
54
67
Fork
You've already forked Longshot
 71
Code Issues 124 Pull requests 196 Projects Releases 8 Packages Wiki Activity Actions 442

WIP: docs(tested): record Deck transition and clock measurements #470

Draft
zeldaootr wants to merge 3 commits from zeldaootr/Longshot:deck-transition-evidence into main
pull from: zeldaootr/Longshot:deck-transition-evidence
merge into: MagicBeanDev:main
Conversation 0 Commits 3 Files changed 12 +36
zeldaootr commented 2026-11-14 16:04:20 +00:00
First-time contributor

Why

Steam Deck OLED runs stopped under memory pressure when entering Hyrule Field on RC3. A second problem left the GPU at 200 MHz after a failed suspend, which obscured the performance of the recovered system.

What changed

Twelve short test records cover baseline, corrected guest memory accounting, sleep/wake recovery and the recorder-thread comparison, one exploratory affinity run, and a GPU timing breakdown of the Field entrance (RX_VK_PASS_TIMING=2: 27.16 ms GPU time a frame, 8.04 ms of it compute dispatches; instrumentation affects timing). main already includes the accounting change (a4c77174, #324).

Flags and settings

None.

Measurements

main @ cf605c85 and this documentation-only PR @ f2b46643 have identical runtime code. Runs used RC3 with both guest-reporting modes in one executable and the stock renderer. On SteamOS 3.9.5, RADV VANGOGH, Mesa 26.2.0-devel, 16 GB, 1280×720, frame generation off, a copied child Kokiri save was teleported to the Field. The low-memory guard stopped all three legacy-report runs. All five default-renderer corrected-report runs finished the 45 s stationary sample. At Kokiri the first two paired runs had 1,507 and 1,566 MiB less guest backing with the corrected report. The GPU stayed at 200 MHz during a 6.03 FPS sample. Following a successful deep sleep and Bluetooth wake the same corrected build reached 20.47 FPS. One exploratory run with the reserved guest CPU core released (HOS_RESERVE_CORE=0) measured 20.73 FPS; one run is too small to justify changing the default. See the individual rows for settings and all comparison arms.

Testing

Tested: The run records passed tests/test_tested_configurations.py. The guard stopped the old-report runs before an actual kernel OOM. Full suite on this branch: 472 passed, 5 failed, 82 skipped. Failures: test_bake_portability, test_lift_cache, test_menu_keys, test_module_ids, test_pad_layout. All of these also failed on unmodified main (cf605c85) in this environment.

Not tested: Windows and other GPUs.

Needs other testers: None: records only.

Screenshots

Nothing on screen changes.

Risk and rollback

This changes measurement records only. Revert the documentation commit to remove them.

Reviewer notes

This provides Deck evidence for existing code and for the separate suspend problem. The recorder comparison found no repeatable increase at the entrance.

Issues

Related hardware report: https://github.com/ValveSoftware/SteamOS/issues/2964

Checklist

For everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description).
  • Rebased on current main. One commit behind: main gained dc390e59 (crash records, unrelated); rebased before ready.
  • python -I -B tests/run_all.py run and passing (any failure that also fails on main is named above).
  • Tested in the game, or what wasn't is named under Testing.
  • Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests).
  • Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
  • 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.

If applicable

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md; no appended row or assembled view).
  • Docs updated.
## Why Steam Deck OLED runs stopped under memory pressure when entering Hyrule Field on RC3. A second problem left the GPU at 200 MHz after a failed suspend, which obscured the performance of the recovered system. ## What changed Twelve short test records cover baseline, corrected guest memory accounting, sleep/wake recovery and the recorder-thread comparison, one exploratory affinity run, and a GPU timing breakdown of the Field entrance (`RX_VK_PASS_TIMING=2`: 27.16 ms GPU time a frame, 8.04 ms of it compute dispatches; instrumentation affects timing). `main` already includes the accounting change (a4c77174, #324). ## Flags and settings None. ## Measurements `main` @ cf605c85 and this documentation-only PR @ f2b46643 have identical runtime code. Runs used RC3 with both guest-reporting modes in one executable and the stock renderer. On SteamOS 3.9.5, RADV VANGOGH, Mesa 26.2.0-devel, 16 GB, 1280×720, frame generation off, a copied child Kokiri save was teleported to the Field. The low-memory guard stopped all three legacy-report runs. All five default-renderer corrected-report runs finished the 45 s stationary sample. At Kokiri the first two paired runs had 1,507 and 1,566 MiB less guest backing with the corrected report. The GPU stayed at 200 MHz during a 6.03 FPS sample. Following a successful deep sleep and Bluetooth wake the same corrected build reached 20.47 FPS. One exploratory run with the reserved guest CPU core released (`HOS_RESERVE_CORE=0`) measured 20.73 FPS; one run is too small to justify changing the default. See the individual rows for settings and all comparison arms. ## Testing **Tested:** The run records passed `tests/test_tested_configurations.py`. The guard stopped the old-report runs before an actual kernel OOM. Full suite on this branch: 472 passed, 5 failed, 82 skipped. Failures: `test_bake_portability`, `test_lift_cache`, `test_menu_keys`, `test_module_ids`, `test_pad_layout`. All of these also failed on unmodified `main` (cf605c85) in this environment. **Not tested:** Windows and other GPUs. **Needs other testers:** None: records only. ## Screenshots Nothing on screen changes. ## Risk and rollback This changes measurement records only. Revert the documentation commit to remove them. ## Reviewer notes This provides Deck evidence for existing code and for the separate suspend problem. The recorder comparison found no repeatable increase at the entrance. ## Issues Related hardware report: https://github.com/ValveSoftware/SteamOS/issues/2964 ## Checklist ### For everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`). - [ ] Rebased on current `main`. One commit behind: `main` gained dc390e59 (crash records, unrelated); rebased before ready. - [x] `python -I -B tests/run_all.py` run and passing (any failure that also fails on `main` is named above). - [x] Tested in the game, or what wasn't is named under Testing. - [x] Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests). - [ ] Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [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. ### If applicable - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`; no appended row or assembled view). - [x] Docs updated. 
Assisted-by: OpenAI Codex
Assisted-by: OpenAI Codex
record the Field GPU timing breakdown
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
Details
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
Details
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
Details
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
Details
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Details
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Details
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Details
Website / Website on Cloudflare (pull_request) Blocked by required conditions
Details
PR description / Description follows the template (pull_request_target) Successful in 26s
Details
Website / Website on Cloudflare (pull_request_target) Has been skipped
Details
5a87e972a5 
Assisted-by: OpenAI Codex
Some checks are pending
CI / Conventional Commit title (pull_request) Blocked by required conditions
Details
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
Details
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
Details
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
Details
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Details
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Details
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Details
Website / Website on Cloudflare (pull_request) Blocked by required conditions
Details
PR description / Description follows the template (pull_request_target) Successful in 26s
Details
Website / Website on Cloudflare (pull_request_target) Has been skipped
Details
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 'deck-transition-evidence:zeldaootr-deck-transition-evidence'
git switch 'zeldaootr-deck-transition-evidence'
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area/accessibility
Barriers for people with disabilities

  
area/audio
Sound and music

  
area/input
Controllers, keyboard, mouse

  
area/install
Installing, updating, building from your game

  
area/menu
In-game menu and settings

  
area/renderer
Vulkan renderer, shaders, effects

  
area/saves
Save files

  
area/upscaling
DLSS, FSR, frame generation

  
good first issue
A good start for a new contributor

  
gpu/amd
AMD GPUs

  
gpu/igpu
Integrated GPUs

  
gpu/intel
Intel GPUs

  
gpu/nvidia
NVIDIA GPUs

  
help wanted
Extra hands or knowledge wanted

  
kind
bug
 Something doesn't work as it should

  
kind
chore
 Build, CI, dependencies, tidying

  
kind
docs
 Documentation

  
kind
feature
 A new feature or an improvement

  
kind
performance
 Frame rate, frame time, loading, memory

  
kind
question
 A question rather than a change

  
needs measurements
Waiting for before/after measurements

  
platform/linux
Linux only

  
platform/steam-deck
Steam Deck

  
platform/windows
Windows only

  
preview
Maintainers: deploy a preview of this PR's website (read its changes first). Removed after the run.

  
priority
critical
 Crashes, data loss, or blocks most players

  
priority
high
 Important: next in line

  
priority
low
 Nice to have

  
status
blocked
 Waits on something else first

  
status
confirmed
 Reproduced or agreed on

  
status
duplicate
 Already reported or proposed

  
status
invalid
 Not a problem in this project

  
status
needs-info
 Waiting for more information from the reporter

  
status
wontfix
 Will not be worked on

  
testing wanted
Wanted: a test on other hardware (posts a test request in #test-requests)

No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!470
No description provided.