No ATI address on the GL_R11F_G11F_B10F? In anycase, I've narrowed down the other issue listed below..."A more significant issue" about the draw buffers. Note, this works on OpenGL 2.1(removing the fancy opengl 3.x stuff to test), but not 3.2 and above (not sure about 3.0). I have determined that the buffers are indeed getting written as if I blit them to FBO 0 I can see the data. The ATI issue deals with having a MRT and then later reading textures in a shader later (I'm still in the same frame). I even tried to unbind my textures from the original FBO, thinking they were locked.. but no success...nothing but black The issues in this post so far appear to be true ATI bugs within their current released driver. I'm still sifting through the spec looking for a magic phrase thats says I'm breaking a rule, but.. looks like I'm inline so far...
Note, I've tried sampler2DMS and without MS to ensure its not a mutlisample bug...
Again, works in NVIDIA, not an ATI, Texture bound to the FBO are getting written to as if I blit the color buffer to FBO 0 I can see the content. It appears to be teh fact of binding to another FBO and trying to read out the texures within the shader that the first FBO filled in.
---------------------------------- END UPDATE---------------------
I'll start adding a list of issues I'm having with an OpenGL 3.x render context over the next few days/weeks.
GL_R11F_G11F_B10F as a multisampled texture generates an opengl Error. (using glTexImage2DMultisample). My other multisampled textures work ok (and are bound to an FBO). In the meantime, I'm using an RGBA16F texture to get around this ATI issue. Our app runs on NVIDIA hardware without a flaw and I've been looking over the opengl specification to try to make sure I'm not in violation of anything.. maybe I am, I would like to support ATI GPUs so hopefully going here makes that happen.
glTexImage2DMultisample is available only if the GL version is 3.2 or greater.
A more significant issue I'm having is that it appears That my colorbuffers are not getting drawn into if using drawelements (multiple render targets with depth_stencil bound to the FBO). I did read where ATI had a bug and the vertex attribute had to be 0, so in GLSL I force that by:
layout(location = 0)in vec3 g_Vertex;
Still not good... All I get is a black screen with no opengl errors
hmm. I just saw this.. I do use a forward compatible context
Installed: Display Driver 55 MB 10.11 11/17/2010
ATI Radeon HD 3450