Game: Pipeline loading freezes on RX 5600 XT after shader cache reaches 100% #1373

Closed
opened 2026-11-17 06:59:55 +00:00 by BeanIssues · 4 comments
Collaborator

Reported on Discord

Longshot version and channel

Longshot v3.0.0-rc.7, release candidate; source e5cea4aa in the log.

What happened

The pipeline screen reached 100% once, then froze for five minutes. After closing and restarting, it froze at 0% on “Loading the shader cache.” The screenshot shows the loading screen at 0%.

Where in the game

Startup, during pipeline/shader-cache loading.

How often

Unknown; reported across two startup attempts.

Graphics card and driver version

AMD Radeon RX 5600 XT, AMD proprietary driver 26.10.1 (log).

CPU, RAM and operating system

AMD Ryzen 5 3600 (12 threads), 16 GB RAM, Windows 11 build 26200 (log).

longshot_log.txt

The log reports a 1664 MB AMD driver shader cache and a 1,405,978 KB Longshot pipeline cache. On close it says the window closed while shaders were prepared and preparation did not stop within 10 seconds; the close census reports zero program/pipeline creations.

Still unknown

Whether it progresses if left longer, exact reproduction frequency, and whether this followed an update or cache change.

Related but different: Longshot#1262 tracked an AMD 0% pipeline-loading stall on different hardware and was closed with a note that it should be fixed in the next release candidate. This RX 5600 XT report describes reaching 100% before freezing, then stalling at 0% on restart.

Attachments

  • longshot_log.txt from Discord message 1572144041867350057.
  • Screenshot_2026-11-17_003950.png from Discord message 1572139619653525568.
Reported on [Discord](https://discord.com/channels/1569849200047427645/1570784344241340417/1572139619653525568) ## Longshot version and channel Longshot v3.0.0-rc.7, release candidate; source e5cea4aa in the log. ## What happened The pipeline screen reached 100% once, then froze for five minutes. After closing and restarting, it froze at 0% on “Loading the shader cache.” The screenshot shows the loading screen at 0%. ## Where in the game Startup, during pipeline/shader-cache loading. ## How often Unknown; reported across two startup attempts. ## Graphics card and driver version AMD Radeon RX 5600 XT, AMD proprietary driver 26.10.1 (log). ## CPU, RAM and operating system AMD Ryzen 5 3600 (12 threads), 16 GB RAM, Windows 11 build 26200 (log). ## longshot_log.txt The log reports a 1664 MB AMD driver shader cache and a 1,405,978 KB Longshot pipeline cache. On close it says the window closed while shaders were prepared and preparation did not stop within 10 seconds; the close census reports zero program/pipeline creations. ## Still unknown Whether it progresses if left longer, exact reproduction frequency, and whether this followed an update or cache change. Related but different: Longshot#1262 tracked an AMD 0% pipeline-loading stall on different hardware and was closed with a note that it should be fixed in the next release candidate. This RX 5600 XT report describes reaching 100% before freezing, then stalling at 0% on restart. ## Attachments - `longshot_log.txt` from Discord message 1572144041867350057. - `Screenshot_2026-11-17_003950.png` from Discord message 1572139619653525568.
Author
Collaborator

Files from the Discord report:

Files from the Discord report: - [longshot_log.txt](https://git.magicbean.dev/attachments/3de0f296-d415-49af-8fab-e4eefc4883b5) - [Screenshot_2026-11-17_003950.png](https://git.magicbean.dev/attachments/52cf9334-39ed-46f3-adf5-7c2905da48cb)

Additional affected hardware, with a startup workaround tested on the same installation.

System: Longshot v3.0.0-rc.7, source e5cea4aa as reported in the game log; Windows 11 build 26300; Radeon RX 5700 XT 8 GB, AMD proprietary driver 26.10.1; Ryzen 7 5700X3D (16 threads), 32 GB RAM. Output 2560×1440.

Observed: after updating, repeated starts remained at 0%, “Loading pipelines / Loading the shader cache,” until closed. An earlier attempt's log reached 100% but did not finish startup. This closely matches the sequence in this issue.

Tests on the same rc.7 installation and existing caches:

Startup mode Observed result
Default, no test switches Remained at 0%; window closed after waiting.
Only RX_VK_PCACHE_LOAD=0 Still remained at 0%; closed after approximately two minutes.
Only RX_VK_LOAD=start Passed pipeline loading and reached the rendered title sequence; I confirmed it was working.

No cache deletion, driver change, rebuild or downgrade was performed between these trials. RX_VK_LOAD=start has now been saved for future launches, but only one successful launch with it has been observed so far. This is a workaround observation, not a confirmed root cause or a fully validated fix.

Selected log evidence from a default failed start (local paths omitted):

[hos host] vk: program cache <game>/cache/longshot_programs.bin: 47798 program keys kept, 7846304 KB
[hos host] vk: the driver's shader cache has 48 of 48 noted pipelines asked (a sample, in 103 ms)
[hos host] vk: pipeline cache file read: not Linux with NVIDIA's own driver
[hos host] vk: pipeline cache <game>/cache/longshot_vk_pipelines.bin (1430618 KB)
[hos host] vk: the window was closed while the shaders were prepared: stopping, what is done is kept
[hos host] vk: the preparation did not stop within 10 s: closing anyway

The cache-file bypass trial logged pipeline cache file not read: RX_VK_PCACHE_LOAD says so (RX_VK_PCACHE_LOAD=0), confirming that switch was applied. The successful launch's log is still buffered while the game is running, so I am not attaching a complete successful-run log yet. I have not checked whether the default path recovers after the successful start launch, or tested this on current main.

Additional affected hardware, with a startup workaround tested on the same installation. **System:** Longshot v3.0.0-rc.7, source `e5cea4aa` as reported in the game log; Windows 11 build 26300; Radeon RX 5700 XT 8 GB, AMD proprietary driver 26.10.1; Ryzen 7 5700X3D (16 threads), 32 GB RAM. Output 2560×1440. **Observed:** after updating, repeated starts remained at 0%, “Loading pipelines / Loading the shader cache,” until closed. An earlier attempt's log reached 100% but did not finish startup. This closely matches the sequence in this issue. **Tests on the same rc.7 installation and existing caches:** | Startup mode | Observed result | | --- | --- | | Default, no test switches | Remained at 0%; window closed after waiting. | | Only `RX_VK_PCACHE_LOAD=0` | Still remained at 0%; closed after approximately two minutes. | | Only `RX_VK_LOAD=start` | Passed pipeline loading and reached the rendered title sequence; I confirmed it was working. | No cache deletion, driver change, rebuild or downgrade was performed between these trials. `RX_VK_LOAD=start` has now been saved for future launches, but only one successful launch with it has been observed so far. This is a workaround observation, not a confirmed root cause or a fully validated fix. Selected log evidence from a default failed start (local paths omitted): ```text [hos host] vk: program cache <game>/cache/longshot_programs.bin: 47798 program keys kept, 7846304 KB [hos host] vk: the driver's shader cache has 48 of 48 noted pipelines asked (a sample, in 103 ms) [hos host] vk: pipeline cache file read: not Linux with NVIDIA's own driver [hos host] vk: pipeline cache <game>/cache/longshot_vk_pipelines.bin (1430618 KB) [hos host] vk: the window was closed while the shaders were prepared: stopping, what is done is kept [hos host] vk: the preparation did not stop within 10 s: closing anyway ``` The cache-file bypass trial logged `pipeline cache file not read: RX_VK_PCACHE_LOAD says so (RX_VK_PCACHE_LOAD=0)`, confirming that switch was applied. The successful launch's log is still buffered while the game is running, so I am not attaching a complete successful-run log yet. I have not checked whether the default path recovers after the successful `start` launch, or tested this on current main.
Author
Collaborator

From Discord:

Reporter confirms Windows 10 with Ryzen 5 3600 and Radeon RX 5600 XT (6 GB). On Longshot v3.0.0-rc.7, screenshot shows 0% at “Loading the shader cache”; first launch stalled at the end of shader loading and a subsequent launch is stuck at the first screen. No driver version or log supplied yet.

From [Discord](https://discord.com/channels/1569849200047427645/1572231779006550046/1572231779006550046): Reporter confirms Windows 10 with Ryzen 5 3600 and Radeon RX 5600 XT (6 GB). On Longshot v3.0.0-rc.7, screenshot shows 0% at “Loading the shader cache”; first launch stalled at the end of shader loading and a subsequent launch is stuck at the first screen. No driver version or log supplied yet.
Author
Collaborator

From Discord:

Reporter shared a second screenshot on 2026-11-17 showing v3.0.0-rc.7 at 100% (36,680 / 36,680 pipelines), status “Getting the game ready.” This confirms the reported 100% stall visually; no additional log or text was provided.

From [Discord](https://discord.com/channels/1569849200047427645/1572268890082517043/1572320922323394630): Reporter shared a second screenshot on 2026-11-17 showing v3.0.0-rc.7 at 100% (36,680 / 36,680 pipelines), status “Getting the game ready.” This confirms the reported 100% stall visually; no additional log or text was provided.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#1373
No description provided.