And I notice that nothing blending ops are functionnal.
So if I activate blending and project two quad, The second quad overlap the second, without blending.
I thinks the problem come from a conflict with the use of FBO and blending on the last Ati driver.
I hope someone will find something to correct it !
What is the config. of your FBO? is it RGB8/RGBA8 or you are using a float texture? If it’s a float texture and you use blending you’ll always going to have theses artifacts… I got a Radeon and I have similar artifacts as soon as blending is ON with either with GL_RGBA16F or GL_RGBA32F on Windows/Linux or Mac (latest driver on all of them). But on NVIDIA no problem, everything is ok. If you are using a float texture just switch back to a 8 bit FBO and everything will be fine.
It looks like floating-point blending is not supported. Blending on float16 textures is supported on X1000 and later. For blending on float32 textures you must have at least HD2000.
I have think the same as your suggestion during my sleep…
But I have done some test :
To setup a 8 bits texture I use GL_RGBA8 (I’m right or not) because I have again the same problem (with a floating point texture or not).
glTexImage2D(texture_rectangle, 0,GL_RGBA8, m_s_TexDec._w, m_s_TexDec._h, 0, GL_RGBA, GL_FLOAT,0); (It’s the good way to create the texture for my FBO ?)
Do you think it exist a method to test if the hardware can support blending on float16 (floating point) texture ?
=> I have done some test, and If I’m doing the blending operation manually by setting the Fbo attached texture in input and output of a shader, the program work good.
So it’s the reason why I think it’s a fp16 blending problem too
Well, GL_FLOAT should not be there if you used RGBA8.
As far as I know, there is no way to check for support. Most probably you have to render something, read the output and compare it with an image of what should have rendered.
Well, GL_FLOAT should not be there if you used RGBA8.
[/QUOTE]
User data format doesn’t matter if the user pointer is NULL and there is no PBO bound. He just created an empty texture object of the size specified by the internalFormat and dimensions.