docs: play on the Steam Deck: what to expect, which switches help, and the clock setting (#716) #968
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
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/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!968
Loading…
Reference in a new issue
No description provided.
Delete branch "omgitsgela/Longshot:docs/steam-deck-playbook"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type: docs · Risk: low · Tested on: Steam Deck LCD (Jupiter, Vangogh), SteamOS holo · Needs: the site preview
Why
Deck players install like it's a desktop PC and then judge the game by their first
minute: auto GPU clocks, an SD-card install, FSR 4 because it is newest, Threaded
rendering because the menu offers it. Most of those choices measure worse on this
hardware, and the two that measure better are two switches nobody tells them about.
This is what we learned running Longshot on a Deck LCD for a week — one page, from
install to the two switches and the one clock line, so a Deck player starts where we
ended.
See #716 (this page is the player-facing half of it; the automation ask stands).
See #386 (SD vs internal drive), #73 (intro movies), #750 (Hyrule Town spin).
What changed
install/steam-deck(
website/src/content-pages.ts, sidebar inwebsite/astro.config.ts), linked fromGetting started under the SteamOS paragraph.
docs/tested/(2026-11-15-steam-deck-lcd-omgitsgela-run03..04):today's main at the worst save (the page's headline expectation) and the intro-movie skip
counts on merged main at stock clocks.
scripts/tested_configurations.pyvalidates both.The launch-state clock arms the page's clock section leans on live on #716 itself, where
the claim lives, not here.
#238's own numbers, the clock line with our paired arms, and the fps a player should
expect per area kind. It tells players to keep FSR 4 off on RDNA2 (measured 15.7 vs
FSR 3.1's 20.6 on Deck) and Threaded off (parity-to-worse on Deck). It states the intro
movie improvement as direction, not a clean single-change number, because the settings
differed between eras — the row says exactly that.
Measurements
Docs only, nothing to measure in code. The two
docs/tested/rows carry the Deckmeasurements themselves, including the honest caveat where a comparison is era-crossing
rather than interleaved (run04's intro line: the pacing engage line did not fire in
those two arms, recorded rather than explained away).
Flags and settings
None added or changed. The page documents two existing switches (
RX_VK_READBACK_LATE,HOS_SHORT_SLEEP_TIMER) at their shipped defaults.Testing
Tested: on the Deck itself — every number on the page comes from scripted arms on
real Deck LCD hardware (rows in
docs/tested/); the fragment validator passes(
scripts/tested_configurations.py, rc 0);tests/run_all.pygives the same resulton this branch and on the rebased base (
533 passed, 20 failed, 90 skippedon both).The 20 are the same host-environment tests that fail on
mainhere, named:test_linux_update,test_lift_cleanup_error,test_make_game_cache,test_bake_portability,test_bug_report,test_crt_options,test_appimage_player_build,test_env_on,test_crash_dialog,test_hardware_report,test_missing_nup,test_link_skip,test_options_budget_once,test_mods_size_table,test_pipeline_tour,test_readback_late,test_run_all_changed,test_vk_pgo,test_walk_key,test_vk_occlusion_queries— none touches this change (docs and website wiring only).Not tested: the website render of the new sidebar entry and page.
Must be tested:
install/steam-deckrenders in the Get started sidebar andthe page's links to
common-issuesandperformance-reportresolve as site links(Test Farm: @Beanstalk docs, the site preview).
power_dpm_force_performance_levelto readhighafterwards (by hand; we measuredthis exact line on our Deck).
Risks
What could break: only the site nav; a wrong slug would 404 the new page.
Turning it off: revert the commit.
Compatibility: Nothing changes for the game.
Issues
See #716
See #386
See #73
See #750
Checklist
Everyone
type(scope): description) of the status line's type.main.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named).third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.docs/tested/for each new measured run (format indocs/tested-configurations.md).WIP until the site preview passes; keeping it WIP is per the template's Needs line.
Possibly related, for context:
WIP: docs: play on the Steam Deck: what to expect, which switches help, and the clock setting (#716)to docs: play on the Steam Deck: what to expect, which switches help, and the clock setting (#716)