OpenGL DSA error; glClearNamedFramebufferfv has no effect in 4.5 context

OpenGL DSA error; glClearNamedFramebufferfv has no effect in 4.5 context

As the title states, the following OpenGL function has no effect:

glClearNamedFramebufferfv(m_glHandle, GL_COLOR, index, &color[0]); 

Replacing it with the non-DSA variant however, works:

glBindFramebuffer(GL_FRAMEBUFFER, m_glHandle);
glClearBufferfv(GL_COLOR, index, &color[0]);

I'm using a OpenGL 4.5 core context, VS2017 project (same happens on VS2015). Works under Linux on the same machine, and under Windows and Linux on other machines.

NOTICE: It is possible that this only happens for  FBO's with multiple attachments!

System Setup Information:
-----------------------------------------

System Used: Lenovo Thinkpad T460p
CPU SKU: i5-6440HQ
GPU SKU: HD530
Processor Line: HQ?
System BIOS Version: N/A
CMOS settings: N/A
Graphics Driver Version: 22.20.16.4729
GOP/VBIOS Version: 1040.0
Operating System: Windows 10 N Professional
OS Version: Build 1506
API: OpenGL 4.5 Core
Occurs on non-Intel GPUs?: No

Steps to Reproduce:
-------------------------------
1. Setup an OpenGL 4.5 core context
2. Create an FBO, attach two color textures
3. Clear an attachment using the named DSA function

Expected Results: The attachment is cleared
-------------------------------

Actual Results: The attachment isn't cleared/possible weird results
-------------------------------

Additional Information:  I use DSA functions for everything else, including FBO creation etc. It is possible that this only happens for  FBO's with multiple attachments! Not verified though, but it doesnt seem to happen for all my FBO's, but it does happen for my G-buffer, which is  has three RGBA16F color attachments, and a Depth24 attachment. All textures has clamp as edgewrap mode, and bilinear filtering (GL_LINEAR for both minification and magnification).
-------------------------------

 

Let me know if you need minimal repro and I'll put together one.

1 post / 0 new
For more complete information about compiler optimizations, see our Optimization Notice.