Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Results 1 to 6 of 6

Thread: glTexStorage2D with GL_TEXTURE_CUBE_MAP on AMD

  1. #1
    Senior Member OpenGL Pro
    Join Date
    Jan 2007
    Posts
    1,213

    glTexStorage2D with GL_TEXTURE_CUBE_MAP on AMD

    Using glTexStorage2D with a target of GL_TEXTURE_CUBE_MAP gives me GL_INVALID_ENUM under AMD, latest (12.8) drivers. The full call is:
    Code :
    glTexStorage2D (GL_TEXTURE_CUBE_MAP, 1, GL_RGBA8, size, size);
    where size has a value of 256. Generating the same cubemap with regular glTexImage2D calls works. Both also work perfectly fine on NVIDIA. The other glTexStorage calls I use (with GL_TEXTURE_2D and GL_TEXTURE_2D_ARRAY) also work perfectly fine on both; this is just restricted to cubemaps and seems an obvious driver bug.

    Can anyone cross-check and confirm?

    The spec and documentation are confusing here. Both the GL_ARB_texture_storage page and the GL spec itself define GL_TEXTURE_CUBE_MAP as a valid target; the man page does not list it among the valid values for target but yet does provide it in the "glTexStorage2D is equivalent to..." examples.

  2. #2
    Advanced Member Frequent Contributor
    Join Date
    Dec 2007
    Location
    Hungary
    Posts
    985
    It is a driver bug, but maybe the latest driver already has it fixed.

    Btw, your use is correct so it seems that the man page is incorrect.
    Disclaimer: This is my personal profile. Whatever I write here is my personal opinion and none of my statements or speculations are anyhow related to my employer and as such should not be treated as accurate or valid and in no case should those be considered to represent the opinions of my employer.
    Technical Blog: http://www.rastergrid.com/blog/

  3. #3
    Senior Member OpenGL Guru
    Join Date
    May 2009
    Posts
    4,948
    The spec and documentation are confusing here. Both the GL_ARB_texture_storage page and the GL spec itself define GL_TEXTURE_CUBE_MAP as a valid target; the man page does not list it among the valid values for target but yet does provide it in the "glTexStorage2D is equivalent to..." examples.
    Maybe you should use something a bit more up-to-date.

  4. #4
    Senior Member OpenGL Pro
    Join Date
    Jan 2007
    Posts
    1,213
    Quote Originally Posted by Alfonse Reinheart View Post
    Maybe you should use something a bit more up-to-date.
    Pardon?

    Are you referring to the documentation or to the API call? If the former then the point that one piece of documentation is in error still stands, and besides, it's completely irrelevant to the matter of a driver bug - no matter how beautiful or correct the documentation may or may not be, the driver bug still exists. If the latter, then you should read the OP again.

  5. #5
    Senior Member OpenGL Guru
    Join Date
    May 2009
    Posts
    4,948
    If the former then the point that one piece of documentation is in error still stands, and besides, it's completely irrelevant to the matter of a driver bug
    Yes, it is irrelevant to the driver bug. But he asked about the docs, so I answered about the docs.

  6. #6
    Senior Member OpenGL Pro
    Join Date
    Jan 2007
    Posts
    1,213
    It wasn't a question about the docs, it was pointing out an error in one of them.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •