You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Windows transparent margins composite as black: bundled GLFW redirection alpha is uninitialized #109
Windows 11 build 26200, NVIDIA RTX 3070 Ti Laptop GPU, driver 32.0.15.9174, MSVC 19.44 x64. EUI dev 89c2d0f.
Build and launch the GLFW/OpenGL transparent_window_viewer fixture. Its 36px outer margin intermittently becomes black even though framebufferTransparent is true. The user confirmed black margins on the actual desktop. Mirage reproduces black rounded corners with the same dependency.
Confirmed isolation and repair
Instrumenting the actual fixture reports corner RGBA=0,0,0,0 with glGetError=0. Clearing the GL default framebuffer was an initial hypothesis; it did not reliably fix the real fixture and has been discarded. A controlled compositor test can also pass on the old code when DWM's backing allocation happens to be zeroed, which explains the intermittent behavior.
The missing initialization is in GLFW's Win32 DWM redirection surface, independently of GL framebuffer alpha. GLFW already tracks this issue in glfw/glfw#2816 and proposed fix glfw/glfw#2815. The bundled 3.4 windowProc has only a damage notification for WM_PAINT and does not define that surface's alpha.
Backporting the small transparent-only WM_PAINT PatBlt(BLACKNESS) repair restores actual desktop transparency on this machine: the formerly black outer margin now shows the wallpaper and desktop icons. Opaque window handling, renderer framebuffer and application geometry stay unchanged; no region crop or color key is used.
A compositor regression uses an owned known-color background and cached UI rendering. Four backend Release build/test checks and relevant fixture inspection are in progress. The separate existing Windows SDL2 compilation blocker is tracked in #110 so it can be reviewed independently.
changed the title [-]Windows: transparent OpenGL cache presentation can show black margins on NVIDIA[/-][+]Windows transparent margins composite as black: bundled GLFW redirection alpha is uninitialized[/+]on Oct 14, 2026
Follow-up: the user installed the patched Mirage payload and still reproduces four black corners intermittently. The installed binary SHA256 exactly matches the patched package, so this is not an old executable. The earlier local fixture/probe result proves initialization in that tested path, but does not prove the full intermittent failure is resolved. PR #112 is still draft, now explicitly related to this issue rather than closing it. GLFW #2815 remains open; Wixely/CupriFace#212 describes a similar confirmed PatBlt-but-black result. No causal attribution to a particular GPU/virtual adapter is established. Mirage will protect its fixed 12px product contour in its private Windows adapter while the generic alpha issue remains open; that is not being submitted as a general GLFW transparency fix.
I think this is the same cause as Wixely/CupriFace#212: when the built-in panel is driven by the iGPU, the NVIDIA OpenGL driver presents through DXGI and picks a flip-model present, which doesn't show DWM per-pixel transparency. It makes that choice once per window, at the first swap, so it can depend on which display the window opens on, or on the laptop's hybrid/dGPU-only mode. That might be the intermittency. Details and a proposed GLFW fix are at glfw/glfw#2924. If the user can check whether the black corners only show up on the built-in panel, or try a GLFW build with that PR, I'd be very interested in the result.
Activity
[-]Windows: transparent OpenGL cache presentation can show black margins on NVIDIA[/-][+]Windows transparent margins composite as black: bundled GLFW redirection alpha is uninitialized[/+]Linductor-alkaid commentedon Oct 14, 2026
Follow-up: the user installed the patched Mirage payload and still reproduces four black corners intermittently. The installed binary SHA256 exactly matches the patched package, so this is not an old executable. The earlier local fixture/probe result proves initialization in that tested path, but does not prove the full intermittent failure is resolved. PR #112 is still draft, now explicitly related to this issue rather than closing it. GLFW #2815 remains open; Wixely/CupriFace#212 describes a similar confirmed PatBlt-but-black result. No causal attribution to a particular GPU/virtual adapter is established. Mirage will protect its fixed 12px product contour in its private Windows adapter while the generic alpha issue remains open; that is not being submitted as a general GLFW transparency fix.
jeweg commentedon Nov 6, 2026
I think this is the same cause as Wixely/CupriFace#212: when the built-in panel is driven by the iGPU, the NVIDIA OpenGL driver presents through DXGI and picks a flip-model present, which doesn't show DWM per-pixel transparency. It makes that choice once per window, at the first swap, so it can depend on which display the window opens on, or on the laptop's hybrid/dGPU-only mode. That might be the intermittency. Details and a proposed GLFW fix are at glfw/glfw#2924. If the user can check whether the black corners only show up on the built-in panel, or try a GLFW build with that PR, I'd be very interested in the result.