Install: Intel Arc A730 shader and pipeline preparation takes hours #1706

Open
opened 2026-11-19 04:36:28 +00:00 by BeanBot · 4 comments
Member

Reported on Discord

What happened

The reporter is building Longshot v3.0.0 in Longshot Launcher and shader preparation is taking an extreme amount of time. At the screenshot, the launcher showed 88% overall, shader preparation at 69%, elapsed 1:14:15, with about 32 minutes estimated remaining. A separate loading-screen screenshot for Longshot v3.0.0-rc.7 showed pipeline loading at 12,750 / 36,682 (34%) with about 1,187 minutes remaining. The reporter observed GPU utilization at 5% (70 °C). They reinstalled, selected side-by-side shader building, and updated the driver; shader preparation still took a long time. A screenshot later showed the launcher apparently unresponsive at 62% of building v3.0.0-rc.8 (about 6 minutes remaining); the visible log reports preparation using 10 workers on a 20-CPU system and Intel shader compilation side by side. The reporter eventually built it and began in-game shader preparation.

The reporter then said the game loads the intro, drops FPS and freezes on a black screen. The attached crash report is for v3.0.0 release, Windows 11 build 26300, Vulkan, Intel Arc A730M driver 101.9175, i7-12700H and 16 GB RAM. It reports an unclean end (no crash/device-lost record), and the report says it may have been stopped externally or by the system, often due to memory exhaustion. It does not establish OOM as the cause. The game map at report time is KokiriForest_Child. Settings include handheld profile, 1280x800 output, and GPU device 1; the reporter says the intro played perfectly before the FPS drop and freeze.

What they used / versions

Longshot Launcher nightly 140 · 87b70727 was shown during build; the build screen showed v3.0.0-rc.8. The crash report is for Longshot v3.0.0 Release (source 87cb36aa). Driver version 32.0.101.9175 WHQL, released 2026-11-04.

System

Intel Arc A730M Graphics, driver 101.9175; Intel Iris Xe also appears in the device list. Windows 11 build 26300, 12th Gen Intel Core i7-12700H (20 threads), 16 GB RAM.

Not known yet

  • Whether Windows or Longshot logged an actual memory-pressure event; the crash report only records an unclean termination.
  • Whether the black-screen freeze recurs, how long it lasts, and whether the game eventually exits or recovers.
  • Full game-folder logs/longshot_log.txt covering the freeze and performance/profile measurements during the drop.
  • The exact game build that first experienced the black-screen freeze (the report is v3.0.0 Release, although the conversation described the preceding RC build process).

Attachments

The crash report from Discord message 1572868089404465353 is attached as message.txt.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1570937947505823793/1572832491847286885) ### What happened The reporter is building Longshot v3.0.0 in Longshot Launcher and shader preparation is taking an extreme amount of time. At the screenshot, the launcher showed 88% overall, shader preparation at 69%, elapsed 1:14:15, with about 32 minutes estimated remaining. A separate loading-screen screenshot for Longshot v3.0.0-rc.7 showed pipeline loading at 12,750 / 36,682 (34%) with about 1,187 minutes remaining. The reporter observed GPU utilization at 5% (70 °C). They reinstalled, selected side-by-side shader building, and updated the driver; shader preparation still took a long time. A screenshot later showed the launcher apparently unresponsive at 62% of building v3.0.0-rc.8 (about 6 minutes remaining); the visible log reports preparation using 10 workers on a 20-CPU system and Intel shader compilation side by side. The reporter eventually built it and began in-game shader preparation. The reporter then said the game loads the intro, drops FPS and freezes on a black screen. The attached crash report is for v3.0.0 release, Windows 11 build 26300, Vulkan, Intel Arc A730M driver 101.9175, i7-12700H and 16 GB RAM. It reports an unclean end (no crash/device-lost record), and the report says it may have been stopped externally or by the system, often due to memory exhaustion. It does not establish OOM as the cause. The game map at report time is KokiriForest_Child. Settings include handheld profile, 1280x800 output, and GPU device 1; the reporter says the intro played perfectly before the FPS drop and freeze. ### What they used / versions Longshot Launcher nightly 140 · 87b70727 was shown during build; the build screen showed v3.0.0-rc.8. The crash report is for Longshot v3.0.0 Release (source 87cb36aa). Driver version 32.0.101.9175 WHQL, released 2026-11-04. ### System Intel Arc A730M Graphics, driver 101.9175; Intel Iris Xe also appears in the device list. Windows 11 build 26300, 12th Gen Intel Core i7-12700H (20 threads), 16 GB RAM. ### Not known yet - Whether Windows or Longshot logged an actual memory-pressure event; the crash report only records an unclean termination. - Whether the black-screen freeze recurs, how long it lasts, and whether the game eventually exits or recovers. - Full game-folder `logs/longshot_log.txt` covering the freeze and performance/profile measurements during the drop. - The exact game build that first experienced the black-screen freeze (the report is v3.0.0 Release, although the conversation described the preceding RC build process). ### Attachments The crash report from Discord message 1572868089404465353 is attached as `message.txt`.
Author
Member

Files from the Discord report:

Files from the Discord report: - [image.png](https://git.magicbean.dev/attachments/c6d215bc-ce82-4124-90be-4635bbd9b8df) - [image.png](https://git.magicbean.dev/attachments/3f080c77-7bdb-4335-a93d-2f82543ddc1d) - [image.png](https://git.magicbean.dev/attachments/a5656c28-d16b-4508-8241-4058536fe57c)
Author
Member

From #1717 (closed as a duplicate of this one):

The same reporter's v3.0.0 release-candidate run on Windows 11 (build 26300), Intel Arc A730M, driver 101.9175, i7-12700H and 16 GB RAM ended without a crash report while preparing shaders. The log shows pipeline preparation still active after roughly 78 minutes, at about 44% (15,000/34,809), with estimated remaining time fluctuating by hours. This adds evidence the prolonged A730 shader/pipeline preparation can end in an unexpected process termination; the unclean record does not establish whether the cause was OOM or an external/system termination.

From #1717 (closed as a duplicate of this one): The same reporter's v3.0.0 release-candidate run on Windows 11 (build 26300), Intel Arc A730M, driver 101.9175, i7-12700H and 16 GB RAM ended without a crash report while preparing shaders. The log shows pipeline preparation still active after roughly 78 minutes, at about 44% (15,000/34,809), with estimated remaining time fluctuating by hours. This adds evidence the prolonged A730 shader/pipeline preparation can end in an unexpected process termination; the unclean record does not establish whether the cause was OOM or an external/system termination.
Author
Member

Updated with more from Discord: Added crash report/system details and the post-build intro-to-black-screen freeze; attached the crash report. It records an unclean termination but does not prove OOM.

Files:

Updated with more from [Discord](https://discord.com/channels/1569849200047427645/1570937947505823793/1572868089404465353): Added crash report/system details and the post-build intro-to-black-screen freeze; attached the crash report. It records an unclean termination but does not prove OOM. Files: - [message.txt](https://git.magicbean.dev/attachments/2fa0fbe2-286a-4f08-8fcd-0da8e0508249)
Author
Member

From Discord:

The reporter says shader compilation has been running for 40 minutes and was still ongoing; they went for a walk while waiting. No GPU, driver, Longshot version/channel, operating system, or log was provided.

From [Discord](https://discord.com/channels/1569849200047427645/1569849200617726065/1573021789725139035): The reporter says shader compilation has been running for 40 minutes and was still ongoing; they went for a walk while waiting. No GPU, driver, Longshot version/channel, operating system, or 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#1706
No description provided.