Install: Slow shader build on original Steam Deck; resumability unclear #1522

Open
opened 2026-11-18 01:55:46 +00:00 by BeanIssues · 3 comments
Collaborator

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.txt or builder/launcher log
  • SteamOS version and free space
  • Whether “Loading Pipelines 100%” eventually completes, and how long it remains there
  • Whether restarting the build/game resumes or retains compiled shader work

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.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1572426822367445003) ### 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.txt` or builder/launcher log - SteamOS version and free space - Whether “Loading Pipelines 100%” eventually completes, and how long it remains there - Whether restarting the build/game resumes or retains compiled shader work ### 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 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.
Author
Collaborator

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.

From [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1572426822367445003): 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.
Author
Collaborator

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.

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1572426822367445003/1572433825990975670): 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.
Author
Collaborator

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](https://discord.com/channels/1569849200047427645/1570784344241340417/1572433942974570708): 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.
Sign in to join this conversation.
No milestone
No project
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#1522
No description provided.