Windows on ARM (Snapdragon X Elite, Adreno X1-85): "Loading pipelines" takes ~42 min on every start, pipeline cache is not reused #1551

Open
opened 2026-11-18 04:52:14 +00:00 by thorearnthur · 2 comments

Longshot version

v3.0.0-rc.7

Channel

Release candidate

What kind of problem

Something else

What happened

The game now renders and plays after updating the Adreno driver (see below), but the start-up "Loading pipelines" step takes about 42 minutes on EVERY launch. The saved pipeline cache is read but not reused.

Run 1 (empty cache): "Preparing shaders" (38,809 shaders) ~16 min. Precompile: 37,899 noted pipelines + 9,367 compute pipelines built in 2485.1 s. Cache saved (1024.3 MB). The game ran and exited normally.

Run 2 (next start): longshot_vk_pipelines.bin (1048893 KB) is read, but the log says "its pipelines took 2518 s (compiled, not found in the caches)". About 42 minutes again.

Run 3: same behaviour (about 44 min left at 20%).

Every start logs vk: driver shader cache at the start: 0 MB (no folder found).

Questions:

  • Is the Adreno driver rejecting the saved VkPipelineCache data (header/UUID check), or does something in the cache key change between runs?
  • Is there a supported way to skip or shorten the start-up precompile? I see RX_VK_PRECOMPILE in longshot_vk.dll but found no documentation.

Also (for the tested-configurations catalogue): with the older Adreno driver 31.0.152.0 (Vulkan 1.3, "host memory import no") the window stayed black: vk: no VK_EXT_external_memory_host: the guest memory cannot be imported -> renderer startup failed -> display: no renderer. Updating to 31.0.178.0 fixed it (host memory import yes). Log of that run: attached as run0 (old driver, black window).

Gameplay after loading: no crashes or device loss, some stutter (worst frames 56 ms and 216 ms in vk: status lines), consistent with pipelines built on the spot.

Environment: Longshot Launcher v1.0.0-rc.10 (x64 build under Windows x64 emulation; there is no ARM64 build). Mesh shaders: no (compute fallback).

Possibly related: #1156 (same effect with a missing driver shader cache on NVIDIA). I found no existing issue for Adreno / Windows on ARM.

Note: not tested on a nightly build; rc.7 is the newest release candidate I could test.

Where in the game

Start-up "Loading pipelines" screen, before reaching the game

How often

Every time

Graphics card and driver version

Qualcomm Adreno X1-85 (integrated), driver 2026.10.1 (v31.0.178.0), Vulkan 1.4

CPU, RAM and operating system

Snapdragon X Elite X1E78100 (12 cores), 16 GB, Windows 11 Home ARM64 build 26300

Changes from the defaults

No Insert-menu changes, no overlays or injectors. A longshot_env.txt with RX_VK_DEVICE=1 was tried once; it had no effect (the native Adreno device was still used).

longshot_log.txt

Logs attached below as files:

  • run0_old-driver_black-window.txt (older Adreno driver 31.0.152.0, black window)
  • run1_first-start_cache-built.txt (first start, cache built)
  • run2_second-start_cache-not-reused.txt (second start, cache not reused; this is the run before the log of run 3)

Screenshots or video

No response

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version v3.0.0-rc.7 ### Channel Release candidate ### What kind of problem Something else ### What happened The game now renders and plays after updating the Adreno driver (see below), but the start-up "Loading pipelines" step takes about 42 minutes on EVERY launch. The saved pipeline cache is read but not reused. **Run 1 (empty cache):** "Preparing shaders" (38,809 shaders) ~16 min. Precompile: 37,899 noted pipelines + 9,367 compute pipelines built in 2485.1 s. Cache saved (1024.3 MB). The game ran and exited normally. **Run 2 (next start):** `longshot_vk_pipelines.bin (1048893 KB)` is read, but the log says "its pipelines took 2518 s (compiled, not found in the caches)". About 42 minutes again. **Run 3:** same behaviour (about 44 min left at 20%). Every start logs `vk: driver shader cache at the start: 0 MB (no folder found)`. Questions: - Is the Adreno driver rejecting the saved VkPipelineCache data (header/UUID check), or does something in the cache key change between runs? - Is there a supported way to skip or shorten the start-up precompile? I see `RX_VK_PRECOMPILE` in longshot_vk.dll but found no documentation. **Also (for the tested-configurations catalogue):** with the older Adreno driver 31.0.152.0 (Vulkan 1.3, "host memory import no") the window stayed black: `vk: no VK_EXT_external_memory_host: the guest memory cannot be imported` -> `renderer startup failed` -> `display: no renderer`. Updating to 31.0.178.0 fixed it (`host memory import yes`). Log of that run: attached as run0 (old driver, black window). **Gameplay after loading:** no crashes or device loss, some stutter (worst frames 56 ms and 216 ms in `vk: status` lines), consistent with pipelines built on the spot. Environment: Longshot Launcher v1.0.0-rc.10 (x64 build under Windows x64 emulation; there is no ARM64 build). Mesh shaders: no (compute fallback). Possibly related: #1156 (same effect with a missing driver shader cache on NVIDIA). I found no existing issue for Adreno / Windows on ARM. Note: not tested on a nightly build; rc.7 is the newest release candidate I could test. ### Where in the game Start-up "Loading pipelines" screen, before reaching the game ### How often Every time ### Graphics card and driver version Qualcomm Adreno X1-85 (integrated), driver 2026.10.1 (v31.0.178.0), Vulkan 1.4 ### CPU, RAM and operating system Snapdragon X Elite X1E78100 (12 cores), 16 GB, Windows 11 Home ARM64 build 26300 ### Changes from the defaults No Insert-menu changes, no overlays or injectors. A longshot_env.txt with RX_VK_DEVICE=1 was tried once; it had no effect (the native Adreno device was still used). ### longshot_log.txt Logs attached below as files: - run0_old-driver_black-window.txt (older Adreno driver 31.0.152.0, black window) - run1_first-start_cache-built.txt (first start, cache built) - run2_second-start_cache-not-reused.txt (second start, cache not reused; this is the run before the log of run 3) ### Screenshots or video _No response_ ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Collaborator

Possibly related, for context:

  • issue #1156 Game: Deleting NVIDIA shader cache causes pipelines to load every boot and excess RAM usage — Related repeated pipeline compilation after the driver shader cache is unavailable; this report is on NVIDIA, and the issue says its behavior was resolved by a later cache-save fix.
  • issue #1510 The shader cache key includes the size of the program struct, so adding any member to it makes every player prepare all shaders again — Related report on cache keys invalidating shader preparation; the cause is not established as the same as this Adreno cache-reuse failure.
  • PR #903 fix(vk): a start that compiled its noted pipelines writes the pipeline cache before the title — Merged fix to save the Vulkan pipeline cache after startup precompile; relevant to cache persistence, but does not confirm a fix for this Adreno setup.
Possibly related, for context: - issue #1156 Game: Deleting NVIDIA shader cache causes pipelines to load every boot and excess RAM usage — Related repeated pipeline compilation after the driver shader cache is unavailable; this report is on NVIDIA, and the issue says its behavior was resolved by a later cache-save fix. - issue #1510 The shader cache key includes the size of the program struct, so adding any member to it makes every player prepare all shaders again — Related report on cache keys invalidating shader preparation; the cause is not established as the same as this Adreno cache-reuse failure. - PR #903 fix(vk): a start that compiled its noted pipelines writes the pipeline cache before the title — Merged fix to save the Vulkan pipeline cache after startup precompile; relevant to cache persistence, but does not confirm a fix for this Adreno setup.
Author

Thanks for the links. Data from my logs (rc.7, Adreno X1-85, driver 31.0.178.0):

  • #903 is already in my build. Run 2 logs: "its pipelines took 2518 s (compiled, not found in the caches): the pipeline cache not written: nothing new since it was read or last written (1024.3 MB), in 5 ms, before the title".
  • So saving works: run 1 wrote the cache (1024.3 MB, 2921 ms) and run 2 read it (1048893 KB). Still, 37,697 graphics pipelines were compiled again; of 3,623 compute pipelines, 3,537 came from the caches and 4 were compiled.
  • This looks like the driver not returning pipelines from the VkPipelineCache data it is given (or the cache key changing between runs), not a save problem. Is there a log line or switch that shows whether the driver accepts the cache blob?
  • Run 1 also wrote longshot_load_start.txt ("501 listed pipelines were in no cache"), which made run 2 load all programs before the title. I can try RX_VK_LOAD=create next and report back.
Thanks for the links. Data from my logs (rc.7, Adreno X1-85, driver 31.0.178.0): - #903 is already in my build. Run 2 logs: "its pipelines took 2518 s (compiled, not found in the caches): the pipeline cache not written: nothing new since it was read or last written (1024.3 MB), in 5 ms, before the title". - So saving works: run 1 wrote the cache (1024.3 MB, 2921 ms) and run 2 read it (1048893 KB). Still, 37,697 graphics pipelines were compiled again; of 3,623 compute pipelines, 3,537 came from the caches and 4 were compiled. - This looks like the driver not returning pipelines from the VkPipelineCache data it is given (or the cache key changing between runs), not a save problem. Is there a log line or switch that shows whether the driver accepts the cache blob? - Run 1 also wrote longshot_load_start.txt ("501 listed pipelines were in no cache"), which made run 2 load all programs before the title. I can try RX_VK_LOAD=create next and report back.
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#1551
No description provided.