From 336a3672a2fd7a7ad7c262e23c4aa6c82119b450 Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Fri, 18 Sep 2026 18:58:11 +0200 Subject: [PATCH] Say plainly that the shield Cut 3 probe needs a graphics device Under -batchmode -nographics every compute kernel lookup fails with "Kernel 'KInit' not found", which reads like a broken shader and is not one: it cost one agent four reproductions and a wrong 'pre-existing environmental regression' claim, and another agent a contradicting pass. SystemInfo.supportsComputeShaders still reports true against the null device, so the guard tests the device type. Co-Authored-By: Claude Opus 5 --- Assets/Scripts/Editor/ShieldPanelCut3Verify.cs | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Assets/Scripts/Editor/ShieldPanelCut3Verify.cs b/Assets/Scripts/Editor/ShieldPanelCut3Verify.cs index 3cf82a7e2..8be2c8aa2 100644 --- a/Assets/Scripts/Editor/ShieldPanelCut3Verify.cs +++ b/Assets/Scripts/Editor/ShieldPanelCut3Verify.cs @@ -36,6 +36,20 @@ namespace Aetheria.EditorTools public static void Run() { + // This probe dispatches the panel's compute kernels, so it needs a graphics device. + // Under -batchmode -nographics the kernels cannot be looked up and every check dies + // with "Kernel 'KInit' not found", which reads like a broken shader and is not one: + // run this probe without -nographics. Verified 2026-09-18, both ways. + // SystemInfo.supportsComputeShaders still reports true against the null device, so the + // device type is what actually answers this (checked 2026-09-18). + if (SystemInfo.graphicsDeviceType == UnityEngine.Rendering.GraphicsDeviceType.Null) + { + Debug.LogError("[ShieldPanelCut3Verify] FAIL: no graphics device in this session. " + + "This probe needs a graphics device; rerun batchmode without -nographics."); + EditorApplication.Exit(1); + return; + } + bool ok = true; ok &= CheckSpawnFrameInjectionAbsorbs(); ok &= CheckReuseStrikesExistingPanel();