Skip to content

Static success but compile/link or FBO failure ​

Follow one order: loading/versions → routes/active closure → resources/bindings → static interface → matching runtime report → appearance/lifecycle. Change one factor at a time.

Locate the failing layer ​

Preserve the first candidate failure, Program ID, source owner, include/define variant, GL API/driver and native compiler log. Check dialect, precision, version and actual device support. compileContextAvailable=false in GL-free staticReflection explicitly means no driver context.

Inspect and repair ​

DLSHADER0301–0302 locate preprocessing failures and DLABI4006 public shader-interface mismatches. Native compiler text still requires device logs; do not invent a stable code from a message. For FBOs inspect format/extent/location, sample count, drawBuffers and complete rows. Restore a minimal RGBA8 + depth24 topology first.

Recheck and recover ​

Re-export using the report guide. A candidate that never published cannot supply a success report. Preserve the old active generation as a recovery baseline. matched covers recorded Program/FBO rows, not every scene or performance. The W7 runtime record states the observed scope.

Author documentation · Manifest v5 / Scene ABI v2