#2075 fix(vk): the renderer's own compute pipelines are made without the optimizer where Intel's Arc A-series driver refuses it
Commit
Plan (gpt-6.1-terra)
Not planned yet.
⚠️ 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.
In plain words
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.
Asked for
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).
can't test this as asked: 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.
Targets
The plan has no targets yet.
Reports
No reports yet. Each tester posts one when its job ends.
Jobs
No jobs. Jobs are made once the plan is approved.