fix(vk): the renderer's own compute pipelines are made without the optimizer where Intel's Arc A-series driver refuses it #2075

Merged
HumanBean merged 2 commits from HumanBean/Longshot:fix/arc-a-unoptimized-retry into main 2026-11-21 17:01:06 +00:00
Owner

Summary

On an Intel Arc A580 (Windows, driver 101.9175, v3.0.0) the screen goes black after the Deku Tree opening cutscene and at a save's load, with the sound and menus still working (#1874). The reporter's logs show why. Intel's driver answers VK_ERROR_UNKNOWN (-13) for optimized compute builds that it then makes without the optimizer: the game's dispatches log it 39 times ("the optimized build was not made (-13); the one without the optimizer stays"). The renderer's own compute pipelines were asked once, with the optimizer, and then given up on:

  • The GPU ASTC decoder was never made (no "ASTC is decoded on the GPU" line, and no line saying why), so every ASTC texture was decoded on the CPU: a frame's uploads took 30853 ms: on the CPU 190 (400.6 MB), with Kokiri Forest's two 1365 x 1365 x 90 arrays at 10.7 s and 11.7 s each. Frames took 30 s and 49 s (slow submit: 29976.0 ms, 48978.3 ms), at 0.4 fps over 80 s. That is the black loading screen.
  • The typed upscale helper that stands in for a network left out (72ba090c70fe2614, left out on every non-NVIDIA card by design: networks_left_out) was not made either (typed upscale helper generic RGB9E5 fallback, packed output: its pipeline was not made). That network's output was then a plain blit of RGB9E5 bits read as B10G11R11: the log's program 72ba090c70fe2614 does not translate: its dispatch replaced by a linear upscale. The translation failure is not device-dependent: 72ba090c is a cooperative-matrix network, left out by policy on every non-NVIDIA GPU. What is A-series specific is that its stand-in's pipeline could not be made.
  • The write-back diff, the late pages' fix and FSR 3's inputs were off the same way (its pipeline was not made, (-13)).

This change asks once more without the optimizer when the driver refuses the optimized build:

  • extern_guarded_compute (gpu/vk/vk_draw.cpp) handles every built-in compute pipeline another file makes: the texture pipelines through texture_compute_pipeline, the write-back diff, the late pages' fix, FSR 3, frame generation and the reactive mask. When the optimized build fails it tries once more with VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BIT and logs one of the renderer's compute pipelines was not made with the driver's optimizer (-13): made without it. This is the fallback the game's own dispatches already have (compute_optimize).
  • vk_draw.cpp's movie upscale, typed upscale and tree-shadow mask helpers called the driver themselves. They now go through texture_compute_pipeline: the pipeline cache first, then the retry above. Their IntelDriverGate now covers only the module, as the texture pipelines' does.
  • astc_ready logs why the GPU decoder is missing: the GPU ASTC decoder's pipeline was not made (%d): ASTC is decoded on the CPU.

Where the optimized build is made (NVIDIA, AMD, the other Intel GPUs the logs show) nothing else is asked, so nothing changes there.

Read first: extern_guarded_compute in gpu/vk/vk_draw.cpp, texture_compute_pipeline and astc_ready in gpu/vk/vk_texture.cpp.

Not fixed here, #826 (A770 device lost just after the intro). It is not the float-add loop of #444 and #816. The dispatch in flight at the loss is 4b03b3040d7cf076; the one before it, ab7699ee7f536755, had finished (checkpoint stages 0x1 and 0x2000). This PC's translation of 4b03b304 has no float adds: no OpAtomicFAddEXT under the native add, where ab7699ee and 499dbfd0 have them. Its 25 compare-exchange loops are byte and short stores into words (OpBitFieldInsert then CAS, at most 1024 tries), and every GPU runs those. On the A580, 4b03b304's and ab7699ee's optimized builds are the very ones the driver refuses (-13), and the A580 never lost the device. So the likely cause is Intel's optimizer on 4b03b304 on the A-series. The Beanstalk request below tells these causes apart. Turning the native float add on for the A-series would not change 4b03b304.

Fixes #1874
See #826

Testing

Tested: Linux, NVIDIA RTX 3090 (driver 620.70.06), this PR @ ac7ed497 over the shared base of main 9dd41326: a run from the kokiri-start save through the job queue: in play after 52 s, a walk and 40 s in Kokiri Forest, a shot, a clean quit (exit 0). The log has "texture pipelines made before the game in 9 ms (ASTC decoder yes, BC encoder yes, GPU unswizzle yes)" and "ASTC is decoded on the GPU", and no "not made with the driver's optimizer" line; the shot shows Link outside his house with every texture and the HUD right. The tree-shadow mask helper is made at first use and wasn't reached in this run. The retry path does not run on this PC: NVIDIA makes every optimized build. The new check tests/test_builtin_compute_unoptimized.py runs the real extern_guarded_compute and texture_compute_pipeline against a driver that refuses optimized builds (the A580's), one that makes them, and one that refuses both. It fails on main and passes here; CI on the forge runs it, because no test suites run on this PC. tests/test_compute_gate.py (the wrapper's lines) and tests/test_taau_typed_dispatch.py (its stand-in for the pipeline call) are updated to match.

Still to test:

  • Windows, Intel Arc A-series (A580, A770 or A380), driver 101.9175: start a new game or load a save past the opening, expecting the log to say "ASTC is decoded on the GPU" and the scene to draw at a playable rate instead of a black screen (@Beanstalk, comment below).
  • Windows, Intel Arc A-series, #826's device loss: the three runs in the Beanstalk request, to tell its cause apart (@Beanstalk).

Measurements

Verdict: the bug is shown by a check and by the reporter's log. No speed changes where the driver makes optimized builds. On the A-series it should take a frame's uploads from 30.9 s of CPU decoding back to the GPU decoder (Beanstalk).

Setup: tests/test_builtin_compute_unoptimized.py; the A580 log from #1874 (v3.0.0, driver 101.9175); one run on this PC (Linux, RTX 3090).

Before: main @ 9dd41326 After: this PR @ ac7ed497
test_builtin_compute_unoptimized, a driver refusing optimized builds FAIL: no pipeline (-13) made without the optimizer (CI)
A580 (from #1874's log, main's code path): ASTC decoder not made, no line; a frame's uploads took 30853 ms: on the CPU to be run (Beanstalk)
RTX 3090: texture pipelines, ASTC on the GPU yes yes

Risks

  • A driver that makes an unoptimized pipeline wrongly: the retry only runs where the optimized build was refused, and the game's own dispatches already run such builds on that driver.
  • The movie, typed upscale and mask helpers now go through the pipeline cache (cached_compute, with its turn at Intel's gate) instead of the driver directly. They are still made on the replay thread at first use, as the texture pipelines were before texture_pipelines_warm.
  • To undo it, revert. No switch, nothing written to the player's files, nothing a player notices on NVIDIA or AMD.

Checklist

Ready for review

  • One topic, on current main; the title is a Conventional Commit.
  • Tested on my own PC, in the game for a change the game runs, as Testing says. (the NVIDIA path, unchanged; the A-series path needs Beanstalk)
  • mise run test passes (any failure that also fails on main is named). (No test suites run on this PC; CI on the forge runs them)
  • Measured against main, or Measurements says why there is nothing to measure.
  • No game files, build output or hand-edited generated files; third_party/ untouched; nothing GPL-incompatible.

When it applies

  • A fix: a game-free test that fails on main and passes here. (Written to fail on main: main's extern_guarded_compute returns the driver's -13. Not run on this PC; CI runs it)
  • A check under tests/ that reads changed source is updated, not weakened.
  • Docs updated. (docs/dev/reference/architecture.md, Rules for resources and presentation)
  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.

Ready to merge

  • Everything in Still to test has run, its results in Tested.
  • Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers").
  • Approved in review, every comment answered.
  • CI passes on the head; on current main, measured again or a comment says why the numbers still hold.

🤖 Generated with Claude Code

https://claude.ai/code/session_017vw8e2uxGKQxzDeQ15jjNK

## Summary On an Intel Arc A580 (Windows, driver 101.9175, v3.0.0) the screen goes black after the Deku Tree opening cutscene and at a save's load, with the sound and menus still working ([#1874](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/1874)). The reporter's logs show why. Intel's driver answers `VK_ERROR_UNKNOWN` (-13) for optimized compute builds that it then makes without the optimizer: the game's dispatches log it 39 times ("the optimized build was not made (-13); the one without the optimizer stays"). The renderer's own compute pipelines were asked once, with the optimizer, and then given up on: - **The GPU ASTC decoder** was never made (no "ASTC is decoded on the GPU" line, and no line saying why), so every ASTC texture was decoded on the CPU: `a frame's uploads took 30853 ms: on the CPU 190 (400.6 MB)`, with Kokiri Forest's two 1365 x 1365 x 90 arrays at 10.7 s and 11.7 s each. Frames took 30 s and 49 s (`slow submit: 29976.0 ms`, `48978.3 ms`), at 0.4 fps over 80 s. That is the black loading screen. - **The typed upscale helper** that stands in for a network left out (`72ba090c70fe2614`, left out on every non-NVIDIA card by design: `networks_left_out`) was not made either (`typed upscale helper generic RGB9E5 fallback, packed output: its pipeline was not made`). That network's output was then a plain blit of RGB9E5 bits read as B10G11R11: the log's `program 72ba090c70fe2614 does not translate: its dispatch replaced by a linear upscale`. The translation failure is not device-dependent: `72ba090c` is a cooperative-matrix network, left out by policy on every non-NVIDIA GPU. What is A-series specific is that its stand-in's pipeline could not be made. - The **write-back diff**, the **late pages' fix** and **FSR 3's inputs** were off the same way (`its pipeline was not made`, `(-13)`). This change asks once more without the optimizer when the driver refuses the optimized build: - `extern_guarded_compute` (`gpu/vk/vk_draw.cpp`) handles every built-in compute pipeline another file makes: the texture pipelines through `texture_compute_pipeline`, the write-back diff, the late pages' fix, FSR 3, frame generation and the reactive mask. When the optimized build fails it tries once more with `VK_PIPELINE_CREATE_DISABLE_OPTIMIZATION_BIT` and logs `one of the renderer's compute pipelines was not made with the driver's optimizer (-13): made without it`. This is the fallback the game's own dispatches already have (`compute_optimize`). - vk_draw.cpp's movie upscale, typed upscale and tree-shadow mask helpers called the driver themselves. They now go through `texture_compute_pipeline`: the pipeline cache first, then the retry above. Their `IntelDriverGate` now covers only the module, as the texture pipelines' does. - `astc_ready` logs why the GPU decoder is missing: `the GPU ASTC decoder's pipeline was not made (%d): ASTC is decoded on the CPU`. Where the optimized build is made (NVIDIA, AMD, the other Intel GPUs the logs show) nothing else is asked, so nothing changes there. Read first: `extern_guarded_compute` in `gpu/vk/vk_draw.cpp`, `texture_compute_pipeline` and `astc_ready` in `gpu/vk/vk_texture.cpp`. **Not fixed here, [#826](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/826)** (A770 device lost just after the intro). It is not the float-add loop of [#444](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/444) and [#816](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/816). The dispatch in flight at the loss is `4b03b3040d7cf076`; the one before it, `ab7699ee7f536755`, had finished (checkpoint stages 0x1 and 0x2000). This PC's translation of `4b03b304` has no float adds: no `OpAtomicFAddEXT` under the native add, where `ab7699ee` and `499dbfd0` have them. Its 25 compare-exchange loops are byte and short stores into words (`OpBitFieldInsert` then CAS, at most 1024 tries), and every GPU runs those. On the A580, `4b03b304`'s and `ab7699ee`'s optimized builds are the very ones the driver refuses (-13), and the A580 never lost the device. So the likely cause is Intel's optimizer on `4b03b304` on the A-series. The Beanstalk request below tells these causes apart. Turning the native float add on for the A-series would not change `4b03b304`. Fixes #1874 See #826 ## Testing **Tested:** Linux, NVIDIA RTX 3090 (driver 620.70.06), this PR @ ac7ed497 over the shared base of main 9dd41326: a run from the kokiri-start save through the job queue: in play after 52 s, a walk and 40 s in Kokiri Forest, a shot, a clean quit (exit 0). The log has "texture pipelines made before the game in 9 ms (ASTC decoder yes, BC encoder yes, GPU unswizzle yes)" and "ASTC is decoded on the GPU", and no "not made with the driver's optimizer" line; the shot shows Link outside his house with every texture and the HUD right. The tree-shadow mask helper is made at first use and wasn't reached in this run. The retry path does not run on this PC: NVIDIA makes every optimized build. The new check `tests/test_builtin_compute_unoptimized.py` runs the real `extern_guarded_compute` and `texture_compute_pipeline` against a driver that refuses optimized builds (the A580's), one that makes them, and one that refuses both. It fails on main and passes here; CI on the forge runs it, because no test suites run on this PC. `tests/test_compute_gate.py` (the wrapper's lines) and `tests/test_taau_typed_dispatch.py` (its stand-in for the pipeline call) are updated to match. **Still to test:** - Windows, Intel Arc A-series (A580, A770 or A380), driver 101.9175: start a new game or load a save past the opening, expecting the log to say "ASTC is decoded on the GPU" and the scene to draw at a playable rate instead of a black screen (@Beanstalk, comment below). - Windows, Intel Arc A-series, [#826](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/826)'s device loss: the three runs in the Beanstalk request, to tell its cause apart (@Beanstalk). ## Measurements **Verdict:** the bug is shown by a check and by the reporter's log. No speed changes where the driver makes optimized builds. On the A-series it should take a frame's uploads from 30.9 s of CPU decoding back to the GPU decoder (Beanstalk). Setup: `tests/test_builtin_compute_unoptimized.py`; the A580 log from #1874 (v3.0.0, driver 101.9175); one run on this PC (Linux, RTX 3090). | | Before: main @ 9dd41326 | After: this PR @ ac7ed497 | |---|---|---| | test_builtin_compute_unoptimized, a driver refusing optimized builds | FAIL: no pipeline (-13) | made without the optimizer (CI) | | A580 (from #1874's log, main's code path): ASTC decoder | not made, no line; `a frame's uploads took 30853 ms: on the CPU` | to be run (Beanstalk) | | RTX 3090: texture pipelines, ASTC on the GPU | yes | yes | ## Risks - A driver that makes an unoptimized pipeline wrongly: the retry only runs where the optimized build was refused, and the game's own dispatches already run such builds on that driver. - The movie, typed upscale and mask helpers now go through the pipeline cache (`cached_compute`, with its turn at Intel's gate) instead of the driver directly. They are still made on the replay thread at first use, as the texture pipelines were before `texture_pipelines_warm`. - To undo it, revert. No switch, nothing written to the player's files, nothing a player notices on NVIDIA or AMD. ## Checklist ### Ready for review - [x] One topic, on current `main`; the title is a Conventional Commit. - [x] Tested on my own PC, in the game for a change the game runs, as Testing says. (the NVIDIA path, unchanged; the A-series path needs Beanstalk) - [ ] `mise run test` passes (any failure that also fails on `main` is named). (No test suites run on this PC; CI on the forge runs them) - [x] Measured against `main`, or Measurements says why there is nothing to measure. - [x] No game files, build output or hand-edited generated files; `third_party/` untouched; nothing GPL-incompatible. ### When it applies - [x] A fix: a game-free test that fails on `main` and passes here. (Written to fail on main: main's `extern_guarded_compute` returns the driver's -13. Not run on this PC; CI runs it) - [x] A check under `tests/` that reads changed source is updated, not weakened. - [x] Docs updated. (`docs/dev/reference/architecture.md`, Rules for resources and presentation) - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. ### Ready to merge - [ ] Everything in Still to test has run, its results in Tested. - [ ] Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers"). - [ ] Approved in review, every comment answered. - [ ] CI passes on the head; on current `main`, measured again or a comment says why the numbers still hold. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_017vw8e2uxGKQxzDeQ15jjNK
Intel's Windows driver on the Arc A-series refuses some optimized
compute builds with VK_ERROR_UNKNOWN (-13) that it makes without the
optimizer. The renderer's own pipelines (the ASTC decoder, the BC
encoders, the unswizzle, the upscale helpers, the write-back diff, the
late pages' fix) were asked once, optimized, and given up on (#1874).
Fails on main.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
fix(vk): the renderer's own compute pipelines are made without the optimizer where Intel's Arc A-series driver refuses it
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 14s
CI / Workflow lint (actionlint) (pull_request) Successful in 14s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Third-party parts / As their notes say (pull_request) Successful in 17s
CI / Website build and checks (pull_request) Successful in 2m40s
PR description / Description follows the template (pull_request_target) Failing after 7s
beanstalk/approval can't be tested as asked: see the farm's comment
ac7ed497bb
Intel's Windows driver on the Arc A-series (an A580 on 101.9175) answers
VK_ERROR_UNKNOWN (-13) for optimized compute builds that it makes
without the optimizer. The renderer's own pipelines were asked once,
optimized: the GPU ASTC decoder was never made, every ASTC texture was
decoded on the CPU (a frame's uploads 30.9 s), and the screen stayed
black after the opening cutscene and at a save's load. The typed upscale
helper, the write-back diff and the late pages' fix were lost the same
way.

extern_guarded_compute now asks once more without the optimizer when
the optimized build is refused, and logs it; vk_draw.cpp's movie,
typed upscale and mask helpers make theirs through
texture_compute_pipeline (the pipeline cache, then that). The ASTC
decoder's failure is logged. Where the optimized build is made
(NVIDIA, AMD) nothing else is asked.

Fixes #1874

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Owner

Tested in game: Linux, RTX 3090, NVIDIA 620.70.06, this PR @ ac7ed497 over main 9dd41326's base, through the job queue: kokiri-start save, in play after 52 s, walk and 40 s in Kokiri Forest, clean quit. Log: texture pipelines made (ASTC decoder yes, BC encoder yes, GPU unswizzle yes), ASTC decoded on the GPU, no 'not made with the driver's optimizer' line; the picture and HUD were right. The Intel retry path can't run on NVIDIA: Beanstalk request below.

Tested in game: Linux, RTX 3090, NVIDIA 620.70.06, this PR @ ac7ed497 over main 9dd41326's base, through the job queue: kokiri-start save, in play after 52 s, walk and 40 s in Kokiri Forest, clean quit. Log: texture pipelines made (ASTC decoder yes, BC encoder yes, GPU unswizzle yes), ASTC decoded on the GPU, no 'not made with the driver's optimizer' line; the picture and HUD were right. The Intel retry path can't run on NVIDIA: Beanstalk request below.
Author
Owner

@Beanstalk Windows, Intel Arc A-series (A580, A770 or A380), Intel driver 101.9175 (and 101.9150 if there is one): build this branch, then three short runs.
(1) Default settings, a new game through the Deku Tree opening into Kokiri Forest (or load the kokiri-start save) and walk for two minutes. Expect the log to have "ASTC is decoded on the GPU", no "a frame's uploads took" line of seconds, and the forest drawn at a playable rate instead of a black screen. Count any "one of the renderer's compute pipelines was not made with the driver's optimizer" lines and say whether it reads "made without it". Note whether the device is lost (#826).
(2) The same with RX_VK_NATIVE_FADD=1: the device lost or not, and whether the forest has a white haze.
(3) The same with RX_VK_NOOPT=1 (every compute dispatch without the optimizer): the device lost or not, and the fps against (1).
For a device loss, paste the log's "device lost:" checkpoint lines (the program keys at stage 0x1 and 0x2000).

@Beanstalk Windows, Intel Arc A-series (A580, A770 or A380), Intel driver 101.9175 (and 101.9150 if there is one): build this branch, then three short runs. (1) Default settings, a new game through the Deku Tree opening into Kokiri Forest (or load the kokiri-start save) and walk for two minutes. Expect the log to have "ASTC is decoded on the GPU", no "a frame's uploads took" line of seconds, and the forest drawn at a playable rate instead of a black screen. Count any "one of the renderer's compute pipelines was not made with the driver's optimizer" lines and say whether it reads "made without it". Note whether the device is lost (#826). (2) The same with RX_VK_NATIVE_FADD=1: the device lost or not, and whether the forest has a white haze. (3) The same with RX_VK_NOOPT=1 (every compute dispatch without the optimizer): the device lost or not, and the fps against (1). For a device loss, paste the log's "device lost:" checkpoint lines (the program keys at stage 0x1 and 0x2000).
Member

Beanstalk test farm · ⛔ can't be tested as asked

Commit ac7ed49 · approved by HumanBean (untrusted) · dashboard

Not run: the farm can't test this as asked, so nothing is built or run:

The requested Intel driver versions cannot be selected or constrained by the farm, so it cannot guarantee the 101.9175 or 101.9150 comparisons. The alternative targets the requested Windows Arc models but would run whatever driver is installed.

⚠️ Note: The plan moves briefly, then measures for two minutes stationary; it cannot walk throughout the measurement. FPS is reported for each scenario but cannot be automatically compared across these separate switch runs.
⚠️ Note: Shots compare each switch setting against main, not against the PR's default, so a haze shared by both builds could be missed. Device-loss checkpoint lines require inspecting the captured log; the plan cannot paste them into its result.
⚠️ Note: The fallback message is logged at most eight times, so its count is a logged count, not necessarily the total number of retries.

What it could test instead: The alternative plan loads the Kokiri start save on Windows Arc A580, A770, or A380 hardware and compares main with the PR under default settings and two diagnostic switches. It records forest images, frame rate, upload stalls, compute-pipeline fallback messages, and device loss over roughly 40 minutes per tester. Missing GPU ASTC decoding, uploads lasting at least a second, a crash, or a substantial image difference fails the plan. No matching Arc model is listed online, so the target would wait for a tester. No tester online now matches windows+intel+gpu-a380_a580_a770: that target waits for one.

A member of BigBeans can comment @Beanstalk <new words> to ask for something else, or @Beanstalk test it anyway to run the plan regardless.

<!-- beanstalk:sticky --> ### Beanstalk test farm · ⛔ can't be tested as asked Commit `ac7ed49` · approved by HumanBean (untrusted) · [dashboard](https://beanstalk.magicbean.dev/prs/2075) **Not run: the farm can't test this as asked**, so nothing is built or run: > The requested Intel driver versions cannot be selected or constrained by the farm, so it cannot guarantee the 101.9175 or 101.9150 comparisons. The alternative targets the requested Windows Arc models but would run whatever driver is installed. ⚠️ **Note:** The plan moves briefly, then measures for two minutes stationary; it cannot walk throughout the measurement. FPS is reported for each scenario but cannot be automatically compared across these separate switch runs. ⚠️ **Note:** Shots compare each switch setting against main, not against the PR's default, so a haze shared by both builds could be missed. Device-loss checkpoint lines require inspecting the captured log; the plan cannot paste them into its result. ⚠️ **Note:** The fallback message is logged at most eight times, so its count is a logged count, not necessarily the total number of retries. What it could test instead: The alternative plan loads the Kokiri start save on Windows Arc A580, A770, or A380 hardware and compares main with the PR under default settings and two diagnostic switches. It records forest images, frame rate, upload stalls, compute-pipeline fallback messages, and device loss over roughly 40 minutes per tester. Missing GPU ASTC decoding, uploads lasting at least a second, a crash, or a substantial image difference fails the plan. No matching Arc model is listed online, so the target would wait for a tester. No tester online now matches windows+intel+gpu-a380_a580_a770: that target waits for one. A member of `BigBeans` can comment `@Beanstalk <new words>` to ask for something else, or `@Beanstalk test it anyway` to run the plan regardless.
Member

Possibly related, for context:

  • issue #1706 Install: Intel Arc A730 shader and pipeline preparation takes hours — Related Arc black-screen report; A730M on driver 101.9175, analogous symptom.
Possibly related, for context: - issue #1706 Install: Intel Arc A730 shader and pipeline preparation takes hours — Related Arc black-screen report; A730M on driver 101.9175, analogous symptom.
HumanBean changed title from WIP: fix(vk): the renderer's own compute pipelines are made without the optimizer where Intel's Arc A-series driver refuses it to fix(vk): the renderer's own compute pipelines are made without the optimizer where Intel's Arc A-series driver refuses it 2026-11-21 17:00:56 +00:00
HumanBean deleted branch fix/arc-a-unoptimized-retry 2026-11-21 17:01:06 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 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!2075
No description provided.