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 3 123 LastLast
Results 1 to 10 of 166

Thread: Official feedback on OpenGL 3.1 thread

Hybrid View

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

    Official feedback on OpenGL 3.1 thread

    The Khronos(tm) Group announced today it has publicly released the OpenGL(r) 3.1 specification that modernizes and streamlines the cross-platform, royalty-free API for 3D graphics. OpenGL 3.1 includes GLSL(tm) 1.40, a new version of the OpenGL shading language, and provides enhanced access to the latest generation of programmable graphics hardware through improved programmability, more efficient vertex processing, expanded texturing functionality and increased buffer management flexibility.

    OpenGL 3.1 leverages the evolutionary model introduced in OpenGL 3.0 to dramatically streamline the API for simpler and more efficient software development, and accelerates the ongoing convergence with the widely available OpenGL ES mobile and embedded 3D API to unify application development. The OpenGL 3.1 specification enables developers to leverage state-of-the-art graphics hardware available on a significant number of installed GPUs across all desktop operating systems. According to Dr. Jon Peddie of Jon Peddie Research, a leading graphics market analyst in California, the installed base of graphics hardware that will support OpenGL 3.1 exceeds 100 million units. OpenGL 3.0 drivers are already shipping on AMD, NVIDIA and S3 GPUs.

    Concurrently with the release of the OpenGL 3.1 specification, the OpenGL ARB has released an optional compatibility extension that enables application developers to access the OpenGL 1.X/OpenGL 2.X functionality removed in OpenGL 3.1, ensuring full backwards compatibility for applications that require it.

    OpenGL 3.1 introduces a broad range of significant new features including:


    • Texture Buffer Objects - a new texture type that holds a one-dimensional array of texels of a specified format, enabling extremely large arrays to be accessed by a shader, vital for a wide variety of GPU compute applications;
    • Signed Normalized Textures - new integer texture formats that represent a value in the range [-1.0,1.0];
    • Uniform Buffer Objects - enables rapid swapping of blocks of uniforms for flexible pipeline control, rapid updating of uniform values and sharing of uniform values across program objects;
    • More samplers - now at least 16 texture image units must be accessible to vertex shaders in addition to the 16 already guaranteed to be accessible to fragment shaders;
    • Primitive Restart - to easily restart an executing primitive - to efficiently draw a mesh with many triangle strips for example;
    • Instancing - the ability to draw objects multiple times by re-using vertex data to reduce duplicated data and number of API calls;
    • CopyBuffer API - accelerated copies from one buffer object to another, useful for many applications including those that share buffers with OpenCL(tm) 1.0 for advanced visual computing applications.

    Webmaster Khronos.org and OpenGL.org

  2. #2
    Super Moderator Frequent Contributor Groovounet's Avatar
    Join Date
    Jul 2004
    Posts
    934

    Re: Official feedback on OpenGL 3.1 thread

    Oo!

    Unexpected release ... so far so good, I was waiting for uniform buffers, I'm glade it's here! Well still waiting for the actual specifications now ...

    It's not much but if the idea is to release every 6 months ... ***Youhou***

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

    Re: Official feedback on OpenGL 3.1 thread

    The specifications are now available in the OGL registry: http://opengl.org/registry/
    Webmaster Khronos.org and OpenGL.org

  4. #4
    Member Regular Contributor
    Join Date
    Nov 2003
    Location
    Germany
    Posts
    293

    Re: Official feedback on OpenGL 3.1 thread

    i just looked over the specs. very nice and unexpected clean . if OpenGL 3.2 gets the direct state access stuff it will be great.

    great work!

    p.s. one question to the UBO extension: is it possible to have multible uniform buffers at once?

    Code :
    uniform lights
    {
        ...
    }
     
    uniform material
    {
        ...
    }

    this is a question i got from the first fast look at the spec. how does this look like on the host side with multiple UBOs for the buffers?

  5. #5
    Intern Contributor
    Join Date
    Oct 2003
    Posts
    68

    Re: Official feedback on OpenGL 3.1 thread

    How does the ARB_compatibility extension work?

    If the extension is supported, a 3.1 context has all the deprecated stuff still there anyway? Or does an application need to explicitly request backwards compatibility somehow?

  6. #6
    Administrator Regular Contributor
    Join Date
    Aug 2001
    Location
    NVIDIA, Fort Collins, CO, USA
    Posts
    184

    Re: Official feedback on OpenGL 3.1 thread

    > If the extension is supported, a 3.1 context has all the deprecated stuff still there anyway?

    That is correct. Just check for GL_ARB_compatibility in the extension string if you need to use any of the deprecated features.

  7. #7
    Member Regular Contributor
    Join Date
    Apr 2006
    Location
    Irvine CA
    Posts
    299

    Re: Official feedback on OpenGL 3.1 thread

    Quote Originally Posted by Chris Lux
    i just looked over the specs. very nice and unexpected clean . if OpenGL 3.2 gets the direct state access stuff it will be great.

    great work!

    p.s. one question to the UBO extension: is it possible to have multible uniform buffers at once?

    Code :
    uniform lights
    {
        ...
    }
     
    uniform material
    {
        ...
    }

    this is a question i got from the first fast look at the spec. how does this look like on the host side with multiple UBOs for the buffers?
    Should be completely doable but there are hardware limits to be aware of. Also, not that UBO extension was written so that it could apply to some pre-GL3 hardware as well such as Radeon X1000 and GeForce 7 - though availability of the ext on those parts is up to the vendor to decide. On those parts you could quite likely be limited to a single UBO bound per draw - this is my initial guess. But on GL3 hardware the limits are higher... 16 I think ?

  8. #8
    Intern Newbie
    Join Date
    Feb 2000
    Location
    UK
    Posts
    42

    Re: Official feedback on OpenGL 3.1 thread

    Nice one - agreed with ector though: direct state access in 3.2 pls.

    Good stuff.

  9. #9
    Super Moderator OpenGL Lord
    Join Date
    Dec 2003
    Location
    Grenoble - France
    Posts
    5,580

    Re: Official feedback on OpenGL 3.1 thread

    From http://developer.nvidia.com/object/o...ver.html#notes :
    This driver implements all of GLSL 1.30 and all of OpenGL 3.0, and all of OpenGL 3.1 and GLSL 1.40, except for the following functionality:

    * The std140, column_major and row_major layout qualifiers in GLSL 1.40
    * The API call BindBufferRange() ignores the <offset> and <size> parameters. In other words, BindBufferRange() behaves the same as BindBufferBase()
    Can't test on my oldish card, but this sounds already quite complete.

  10. #10

    Re: Official feedback on OpenGL 3.1 thread

    Just dropped by out of self-inflicted exile to say: GOOD JOB, KHRONOS

Posting Permissions

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