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

Open
opened 2026-11-18 01:55:46 +00:00 by BeanBot · 6 comments
Member

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.txt from Discord message 1573444709047607428. It records vk: precompile: its pipelines took 485 s (compiled, not found in the caches) and game performance after load (median 160 FPS).

Still unknown

  • What action/update precedes the supposedly random rebuild, and exact steps/repeatability
  • Whether this log corresponds to the same repeated rebuild symptom, or only the subsequent start
  • SteamOS/Deck details for the separate Deck report; Windows version, CPU and RAM for this PC
  • Builder/launcher log 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 subsequent pipeline loading/resumability.

  • 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.
  • PR #900 (first in nightly-296-d9486a08) prevents Steam Deck Game Mode from recompiling pipelines prepared earlier due to RADV's VRS setting.
  • PR #1689 (first in nightly-580-9de436c2) avoids re-preparation after translator comment/format-only edits.
  • PR #1618 (first in v3.0.0-rc.8) improves progress reporting, but explicitly does not reduce preparation time.
    These known fixes may not explain the reported behavior; the reporter's log is Windows/NVIDIA, not Deck.
Reported on [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1572426822367445003) ### 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.txt` from Discord message 1573444709047607428. It records `vk: precompile: its pipelines took 485 s (compiled, not found in the caches)` and game performance after load (median 160 FPS). ### Still unknown - What action/update precedes the supposedly random rebuild, and exact steps/repeatability - Whether this log corresponds to the same repeated rebuild symptom, or only the subsequent start - SteamOS/Deck details for the separate Deck report; Windows version, CPU and RAM for this PC - Builder/launcher log 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 subsequent pipeline loading/resumability. - 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. - PR #900 (first in nightly-296-d9486a08) prevents Steam Deck Game Mode from recompiling pipelines prepared earlier due to RADV's VRS setting. - PR #1689 (first in nightly-580-9de436c2) avoids re-preparation after translator comment/format-only edits. - PR #1618 (first in v3.0.0-rc.8) improves progress reporting, but explicitly does not reduce preparation time. These known fixes may not explain the reported behavior; the reporter's log is Windows/NVIDIA, not Deck.
Author
Member

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
Member

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
Member

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.
Author
Member

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](https://discord.com/channels/1569849200047427645/1570984952651055114/1573442446266990672): 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.
Author
Member

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.

From [Discord](https://discord.com/channels/1569849200047427645/1573442446266990672/1573442911494742251): 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.
Author
Member

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:

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1573442446266990672/1573444709047607428): 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: - [longshot_log.txt](https://git.magicbean.dev/attachments/37797532-6cc0-48db-be86-d2ba954f78ac) - [image.png](https://git.magicbean.dev/attachments/de64447c-7357-4f5f-b7e4-c377ac683651)
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.