GL_FRAMEBUFFER_SRGB busted in 365.xx and 368.22 ?

I’m seeing a regression in 365.xx and 368.22 on a Quadro K620 and Windows 10/x64 workstation.

I have a framebuffer with SRGB enabled by default and can toggle the flag at runtime with glEnable(GL_FRAMEBUFFER_SRGB).

The same app produces incorrect results in 365.xx and 368.22.

The app’s interaction with GL is rather simple and has worked fine with previous drivers for a couple years.

Huzzah! It is fixed by making sure the alpha depth is set to 0 before creating a window with GLFW:


Drivers up to 364.72 worked fine without zero’ing the alpha depth.

The linear renderbuffer now results in SRGB-correct colors when it’s blitted to the backbuffer.

I have reported this bug to NV OpenGL driver team. Thanks for reporting this issue.