ToastconcernandClaude Opus 4.8 ef7bbfcf4d Windows layer: track the bound shader per context, and log what the compositor draws ...

On a real headset the layer connected but replaced nothing, so the compositor draws its environment through a path
the layer wasn't catching. Track the bound pixel shader per device context (not only the immediate one we hooked, in
case the environment is recorded on a deferred context), name every pixel shader from its .fxo, and the first time
each is drawn log its name and whether it was on our context or another. The 5-second heartbeat now always prints
(home draws, distinct shaders seen here/other, connected). This makes one short headset session show exactly which
shaders and context the environment uses, to aim the fix. The diagnostic stops itself after a few seconds of draws.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-10-21 20:29:41 -05:00

..

d3d11_proxy.def

Frame Home as the real SteamVR environment on a PC (Windows too), not a home app

2026-10-21 19:39:36 -05:00

env_ps.frag

Frame Studio and Frame Home: cross-platform builds

2026-10-21 12:03:25 -05:00

frame_home_layer_d3d11.cpp

Windows layer: track the bound shader per context, and log what the compositor draws

2026-10-21 20:29:41 -05:00

frame_home_layer.cpp

Frame Studio and Frame Home: cross-platform builds

2026-10-21 12:03:25 -05:00