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.
Version
Longshot v3.0.0-rc.7.
Channel
Release candidate.
Where it stopped
During the shader build, the UI stopped accepting clicks. Initially it showed about 83% after about an hour; it was still progressing, with the UI updating every few minutes and advancing by about 1%. The reporter later said it completed: progress from 60% to 90% took almost two hours at 100% CPU usage, then 90% to 100% completed with little CPU usage. After completion, it is now stuck at “Loading Pipelines 100%” and using 100% CPU.
What happened and what was expected
The reporter asks whether the build can be resumed after restarting the launcher/builder because its UI stopped accepting clicks, and wants to avoid losing already compiled shaders. The build progressed slowly and eventually completed; the current report is that loading pipelines is now stuck at 100% with 100% CPU usage. It remains unknown whether restarting resumes shader work or what restarting would retain.
System
Original release Steam Deck hardware. OS version and available free space were not provided.
Log
Not provided.
Still unknown
longshot_log.txtor builder/launcher logRelated
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 the subsequent “Loading Pipelines 100%” state / resumability question.
Longshot PR #1418 (first in nightly-447-03788b38) fixes an unnecessary full pipeline rebuild on a later game start after an update that changed no shaders. The report does not establish that this is the same cause; the reporter is using v3.0.0-rc.7 and the current “Loading Pipelines 100%” state follows the slow build.
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.