From 37f3ed0498b854bc280b31c406b43f21f104a0d0 Mon Sep 17 00:00:00 2001 From: Erik Date: Tue, 28 Jul 2026 07:45:24 +0200 Subject: [PATCH] docs(render): record the 10/10 NVIDIA cross-vendor verdict; adopt the driver-defect conclusion The exact V4c binary - verified by its embedded wb-mesh pipeline literals - rendered ten of ten repeat-gate cycles on a separate NVIDIA PC against the same ACE, same scene, same account, while the AMD box fails 30%+ of identical runs with the defect pinned to this binary at p=0.024. Two GL drivers, one failure. Option B is adopted: GL keeps the legacy world path to V10, the RHI world path ships on Vulkan, and the V4c/V4d GL re-land is closed rather than parked. Co-Authored-By: Claude Fable 5 --- docs/plans/2026-07-27-vulkan-campaign.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/docs/plans/2026-07-27-vulkan-campaign.md b/docs/plans/2026-07-27-vulkan-campaign.md index c148e100..f4f4d03b 100644 --- a/docs/plans/2026-07-27-vulkan-campaign.md +++ b/docs/plans/2026-07-27-vulkan-campaign.md @@ -974,6 +974,29 @@ of a multi-hour bisect: fault reproducing on both backends is a property of the ported path itself, not of a driver's GL stack. +#### 5.5.6 Cross-vendor verdict (2026-07-28): NVIDIA renders the V4c binary 10/10 + +The missing second data point arrived before the Vulkan one. The exact V4c +binary — published from `eb2ba4e5` + `git revert --no-commit 543bc79f`, and +verified to be the V4c build by its embedded `wb-mesh-*` pipeline-name literals, +which the HEAD build on the AMD machine provably lacks — ran the full ten-cycle +repeat-connected gate on a separate NVIDIA PC against the same ACE instance, +same account, same pinned worst-case cell, desktop-witness verdict: + +**10/10 RENDERED.** Ten clean runs bound the NVIDIA failure rate below ~4% at +90% confidence, against a measured 30%+ (up to 5-of-5) on the AMD box, where the +interleaved A/B probe had already pinned the defect to this binary at p≈0.024. + +Same binary, same server, same scene, two GL drivers: only AMD's fails, and it +fails below the API in four independent instruments. **The driver-defect +conclusion is adopted as established** (AMD 26.6.4 GL stack, RX 9070 XT). The +Vulkan world-path measurement remains worth taking when V6 completes — as the +shipping path's own proof, no longer as the discriminator. Per the §5.5.5 +decision rule this selects option (B): the GL backend keeps the legacy raw-GL +world path through to V10 as the documented, scoped fork exception, and the +RHI world path ships on Vulkan. V4c/V4d's GL re-land is closed, not merely +parked; their content returns as the Vulkan world path. + **Sequencing.** V5 and V6 execute next, in that order. **V4t and V4e–V4h are re-sequenced after the verdict**, not before it — V4h in particular cannot be specified until it is known whether "nothing raw-GL remains" is still reachable.