Part of the Khronos Group
OpenGL.org

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Page 1 of 7 123 ... LastLast
Results 1 to 10 of 63

Thread: NVIDIA releases OpenGL 4.3 beta drivers

  1. #1
    Administrator Regular Contributor Khronos_webmaster's Avatar
    Join Date
    Apr 2007
    Location
    Montreal
    Posts
    151

    NVIDIA releases OpenGL 4.3 beta drivers

    NVIDIA is proud to announce the immediate availability of OpenGL 4.3 beta drivers for Windows and Linux.

    You will need any one of the following Fermi based GPU to get access to the full OpenGL 4.3 and GLSL 4.30 functionality:
    Quadro series: 6000, 600, 5000, 410, 4000, 400, 2000D, 2000
    GeForce 600 series: GTX 690, GTX 680, GTX 670, GT 645, GT 640, GT 630, GT 620, GT 610, 605
    GeForce 500 series: GTX 590, GTX 580, GTX 570, GTX 560 Ti, GTX 560 SE, GTX 560, GTX 555, GTX 550 Ti, GT 545, GT 530, GT 520, 510
    GeForce 400 series: GTX 480, GTX 470, GTX 465, GTX 460 v2, GTX 460 SE v2, GTX 460 SE, GTX 460, GTS 450, GT 440, GT 430, GT 420, 405

    For OpenGL 3 capable hardware, these new extensions are provided:
    ARB_arrays_of_arrays
    ARB_clear_buffer_object
    ARB_copy_image
    ARB_ES3_compatibility
    ARB_explicit_uniform_location
    ARB_fragment_layer_viewport
    ARB_framebuffer_no_attachments
    ARB_internalformat_query2
    ARB_invalidate_subdata
    ARB_program_interface_query
    ARB_robust_buffer_access_behavior
    ARB_stencil_texturing
    ARB_texture_buffer_range
    ARB_texture_query_levels
    ARB_texture_storage_multisample
    ARB_texture_view
    ARB_vertex_attrib_binding
    KHR_debug

    For OpenGL 4 capable hardware, these new extensions are provided:
    ARB_compute_shader
    ARB_multi_draw_indirect
    ARB_shader_image_size
    ARB_shader_storage_buffer_object

    The drivers and extension documentation can be downloaded from http://www.nvidia.com/content/devzon...river-4.3.html
    Webmaster Khronos.org and OpenGL.org

  2. #2
    Intern Contributor
    Join Date
    Mar 2010
    Posts
    59
    GLEW 1.9.0 has also been released which includes support for OpenGL 4.3:
    http://glew.sourceforge.net/

    This will make using the new API easier.

  3. #3
    Advanced Member Frequent Contributor
    Join Date
    Dec 2007
    Location
    Hungary
    Posts
    985
    Quote Originally Posted by Piers Daniell View Post
    GLEW 1.9.0 has also been released which includes support for OpenGL 4.3
    Wow! That was the quickest GLEW update in history
    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/

  4. #4
    Member Regular Contributor malexander's Avatar
    Join Date
    Aug 2009
    Location
    Ontario
    Posts
    324
    Just tried out glObjectLabel(), and it doesn't work with GL_BUFFER or GL_TEXTURE - it throws an INVALID_ENUM for both (at least the feedback is nice: "GL_INVALID_ENUM error generated. ObjectLabel: invalid <identifier> enum value"). I also tried GL_TEXTURE_2D just in case, but this didn't work either (nor should it, from the spec).

    It works with GL_FRAMEBUFFER, GL_PROGRAM and GL_SHADER, though - at least it doesn't throw a GL error. However, a later performance message "Program/shader state performance warning: Fragment Shader is going to be recompiled because the shader key based on GL state mismatches." doesn't reference my shader name at all, which seems to defeat the purpose. It'd also be nice to know what part of the GL state it's referring to.

  5. #5
    Senior Member OpenGL Guru
    Join Date
    May 2009
    Posts
    4,948
    It'd also be nice to know what part of the GL state it's referring to.
    It seems to always say this for me. I'm always getting that for any programs I create. But at least it's an initialization-time thing.

  6. #6
    Intern Contributor
    Join Date
    Mar 2010
    Location
    Winston-Salem, NC
    Posts
    62
    I installed NVIDIA beta driver 304.32 on Lubuntu 12.04 Linux using the xorg-edgers PPA so that I wouldn't have to fool with .run scripts and turning off X servers. On my laptop I have an old GeForce 8600M GT card, which is OpenGL 3.3 class HW. The NVIDIA OpenGL driver page says, "For OpenGL 3 capable hardware, these new extensions are provided:" and gives a list of 18 extensions. Unfortunately none of them are shown as available by either glxinfo or nvidia-settings.


    Anyone have OpenGL 3 class HW that's showing the new extensions, on either Windows or Linux?

  7. #7
    Member Regular Contributor malexander's Avatar
    Join Date
    Aug 2009
    Location
    Ontario
    Posts
    324
    Hm, perhaps I will disable that warning.

    Correction to my original post - glObjectName(GL_FRAMEBUFFER, ...) produces an invalid enum as well. I mistook that error for a GL_TEXTURE error.

  8. #8
    Intern Contributor
    Join Date
    Mar 2010
    Posts
    59
    It appears we missed support for GL_TEXTURE, GL_FRAMEBUFFER and GL_RENDERBUFFER. All the others are supported. This is a trivial fix and it'll be in the next beta update next week. Sorry for the trouble and thanks for reporting the bug.

    We'll also audit our error messages and make sure they use the object label instead of the number if it exists. This fix will come later. The extension is still useful because middleware tools can query objects to get names which the app sets. But clearly having the names in the debug_output strings makes sense.

  9. #9
    Member Regular Contributor malexander's Avatar
    Join Date
    Aug 2009
    Location
    Ontario
    Posts
    324
    Thanks! I also wouldn't mind something like "object name (object id)" in the debug output.

  10. #10
    Intern Contributor
    Join Date
    Mar 2010
    Location
    Winston-Salem, NC
    Posts
    62
    What is the best way to file a bug report to NVIDIA for their beta drivers? I used their generic "Submit feedback on an NVIDIA product" form, but the release notes for the driver direct one to an NVIDIA developer site. This site seems to be isolated from the main NVIDIA site; the developer area reached from the main site is different. I used to have an NVIDIA developer account eons ago, but it seems that has lapsed. I don't see any obvious way to create an account for the nvdeveloper.nvidia.com site, and it doesn't accept the username and password I have for the main site. So, I have the feeling that the left hand is separated from what the right hand is doing, and nobody's actually going to read the feedback I just filed. What's the best way?

Tags for this Thread

Posting Permissions

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