GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT 错误

Question

我在 OpenGL 代码中使用 FBO，并且在 GL\_FRAMEBUFFER\_INCOMPLETE\_DUPLICATE\_ATTACHMENT\_EXT。 这是什么原因以及如何解决？

Answer 1

造成这个错误的原因是NVIDIA的glext.h的旧版本，它仍然有这个定义。 而最新版本的 GLEW 则不然。 这会导致您之前编写的或从网上获取的代码出现编译错误。

FBO 的 GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT 定义曾经出现在规范中（因此也出现在头文件中）。 但是，后来它被删除了。 其原因可以在 FBO 扩展规范（查找问题 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.

要修复此错误，请从代码中删除所有 GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT 的使用。

如果您的设置无法做到这一点，请向您的 glext.h 或 glew.h 文件添加一个虚拟定义，如下所示：

#define GL_FRAMEBUFFER_INCOMPLETE_DUPLICATE_ATTACHMENT_EXT 0x8CD8