Install: Slow shader build on original Steam Deck; resumability unclear #1522
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1522
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Reported on Discord
What you used
Longshot Launcher / Builder; the attached log is from running the game.
Version
Longshot nightly-612-89c3d21e (source 52f5212d).
Channel
Nightly.
What happened and what was expected
The reporter says the shader build “rebuilds completly random without doing anything very slowly,” and clarifies this is not limited to Steam Deck. Screenshot from nightly 612 shows “Loading pipelines” at 569 / 42,421 (1%). The attached log later shows the game did load and run: precompile took 485 seconds, and the log reports 37,474 pipelines in the session; this log does not establish what triggered a rebuild or how often it happens.
Earlier report: on Steam Deck the builder UI stopped accepting clicks during slow shader preparation, then completed; after completion, “Loading Pipelines 100%” with high CPU was reported. Whether restarting resumes/retains work is still unknown.
System
This attached log is from Windows, NVIDIA GeForce RTX 5070, NVIDIA driver 621.24. CPU and RAM are not identified in the log excerpt; OS version and free space were not provided. Separate affected hardware is reported as not limited to Steam Deck; details for the original Steam Deck report are still unavailable.
Log
Attached
longshot_log.txtfrom Discord message 1573444709047607428. It recordsvk: precompile: its pipelines took 485 s (compiled, not found in the caches)and game performance after load (median 160 FPS).Still unknown
Related
Longshot #1477 discusses build-time translation of mesh shaders for Deck/AMD, but does not track this report about slow shader compilation during a build or subsequent pipeline loading/resumability.
These known fixes may not explain the reported behavior; the reporter's log is Windows/NVIDIA, not Deck.
From Discord:
The reporter confirms the build completed: progress from 60% to 90% took almost two hours at 100% CPU usage; from 90% to 100% it used only a trivial amount of CPU. The builder's resume behavior remains unconfirmed.
Updated with more from Discord: Added the latest state: after the shader build completed, the game is stuck at “Loading Pipelines 100%” with 100% CPU usage; noted the potentially related but not confirmed PR #1418 and remaining unknowns.
From Discord:
Additional report from the reporter on Intel Arc 730, Windows: Longshot v3.0.0-rc.7's pipeline screen showed 5,796/36,682 (15%) and the reporter said progress had not moved since their earlier screenshots. They also posted a launcher Nightly 128 build screen at 61%, with “Prepare shaders” at 0% after 43:09, and a game pipeline build screen at 4,908/36,682 (43%) with an estimate of about 3398 minutes. Screenshots are in the Discord conversation. Please add profiling/logs and Intel driver version when available; no log was provided.
From Discord:
Additional report from Discord (2026-11-20): on Steam Deck LCD, nightly-613 reportedly loads foliage, while nightlies 625 and 626 do not. Screenshot from nightly-612 shows “Loading pipelines” at 569 / 42,421 (1%). Please assess whether this is related to the report's slow shader/pipeline preparation; foliage regression may be a separate issue.
From Discord:
The reporter clarifies that the slow/repeated shader build is not limited to Steam Deck. No other system details were provided yet; please add the affected hardware/OS and a log when available.
Updated with more from Discord: Added the reporter's Windows/NVIDIA RTX 5070 nightly-612 log and its 485-second precompile, clarified the scope and remaining unknown trigger/repro steps.
Files: