Errors GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT

Question

I use FBO in my OpenGL code and I see compilation errors on GL\_FRAMEBUFFER\_INCOMPLETE\_DUPLICATE\_ATTACHMENT\_EXT . What is the reason for this and how to fix it?

Answer 1

The cause of this error is an older version of NVIDIA glext.h , which still has this definition. While in the latest versions there is no GLEW . This leads to compilation errors in the code that you previously wrote or received from the Internet.

The definition of GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT for the FBO is used in the specification (and therefore in the header files). But he was later removed. The reason for this can be found in the FBO extension specification (see Release 87):

 (87) What happens if a single image is attached more than once to a framebuffer object? RESOLVED: The value written to the pixel is undefined. There used to be a rule in section 4.4.4.2 that resulted in FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT if a single image was attached more than once to a framebuffer object. FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT 0x8CD8 * A single image is not attached more than once to the framebuffer object. { FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT } This rule was removed in version #117 of the EXT_framebuffer_object specification after discussion at the September 2005 ARB meeting. The rule essentially required an O(n*lg(n)) search. Some implementations would not need to do that search if the completeness rules did not require it. Instead, language was added to section 4.10 which says the values written to the framebuffer are undefined when this rule is violated. 

To fix this error, remove all GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT from your code.

If this is not possible in the configuration, add a dummy definition to the glext.h or glew.h file , for example:

 #define GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT 0x8CD8