Shader ownership change
All checks were successful
CI / React UI Build (push) Successful in 11s
CI / Native Windows Build And Tests (push) Successful in 2m52s
CI / Windows Release Package (push) Successful in 2m59s

This commit is contained in:
Aiden
2026-05-12 02:15:03 +10:00
parent 4ea829af85
commit c0d7e84495
12 changed files with 370 additions and 36 deletions

View File

@@ -38,7 +38,8 @@ Included now:
- latest-N system-memory frame exchange
- rendered-frame warmup
- background Slang compile of `shaders/happy-accident`
- render-thread-only GL commit once compiled shader source is ready
- app-owned submission of a completed shader artifact
- render-thread-only GL commit once the artifact is ready
- compact telemetry
- non-GL frame-exchange tests
@@ -106,9 +107,9 @@ Healthy first-run signs:
## Runtime Slang Shader Test
On startup the app begins compiling `shaders/happy-accident` on a background thread.
On startup the app begins compiling `shaders/happy-accident` on a background thread owned by the app orchestration layer.
The render thread keeps drawing the simple motion renderer while Slang compiles. It only attempts the OpenGL shader compile/link once a complete GLSL fragment shader is ready. If either the Slang build or GL commit fails, the app keeps rendering the simple motion fallback.
The render thread keeps drawing the simple motion renderer while Slang compiles. It does not choose packages, launch Slang, or track build lifecycle. It only receives a completed shader artifact and attempts the OpenGL shader compile/link at a frame boundary. If either the Slang build or GL commit fails, the app keeps rendering the simple motion fallback.
Successful handoff signs: