• Advertisement
Sign in to follow this  

OpenGL OpenGL 4.4 spec is published

This topic is 1590 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Well, since I didn't saw any thread about it, here it is:

 

OpenGL 4.4 released.

 

OpenGL registry where you can see the pdfs of the spec.

 

And nVidia's drivers for it (Linux/Windows/x86/x86_64/yaddayadda). There are a few new extensions also available for OpenGL 3 hardware.

Edited by TheChubu

Share this post


Link to post
Share on other sites
Advertisement

I'm excited about ARB_Sparse_Texture, though I'm a little confused as to why they don't support any of the 3-component texture formats.

Share this post


Link to post
Share on other sites

Not a very interesting revision, but the new extensions (sparse texture, bindless texture) are intriguing...

Share this post


Link to post
Share on other sites

Well, since I didn't saw any thread about it, here it is:

 

OpenGL 4.4 released.

 

OpenGL registry where you can see the pdfs of the spec.

 

And nVidia's drivers for it (Linux/Windows/x86/x86_64/yaddayadda). There are a few new extensions also available for OpenGL 3 hardware.

 

Thanks for the heads up.  I'll have to check it out.

Edited by MarekKnows.com

Share this post


Link to post
Share on other sites

I think the biggest improvement is the conformace test. From what i head from who prefer DX over GL is that the drivers sometimes have different behaviours for different cards (with openGL). With this change, all the driver will(?should?) have the same behaviour, making it easier to develop openGL programs.

Share this post


Link to post
Share on other sites

So, OpenGL 4.4 specs have been published, and AMD still doesn't have a [i]working[/i] implementation of OpenGL 4.3. This is wonderful. rolleyes.gif

Share this post


Link to post
Share on other sites

I'm excited about ARB_Sparse_Texture, though I'm a little confused as to why they don't support any of the 3-component texture formats.

GPU hardware hasn't supported 3-component texture formats for a long time (aside from packed formats like DXT1).

If you ask GL to give you an RGB texture, on the GPU it will allocate an RGBA texture and pretend that the alpha channel doesn't exit...

I think the biggest improvement is the conformace test. From what i head from who prefer DX over GL is that the drivers sometimes have different behaviours for different cards (with openGL). With this change, all the driver will(?should?) have the same behaviour, making it easier to develop openGL programs.

Yeah that's something that I always have a whinge about, so this makes me very happy biggrin.png

[the ARB] has created the first set of formal OpenGL conformance tests since OpenGL 2.0 [and] full certification is mandatory for OpenGL 4.4 and onwards

Edited by Hodgman

Share this post


Link to post
Share on other sites

Not gonna comment on the features since I'm still trying to play catch up (this is what happens when you live in a place where any upgrade to a PC ends up costing an entire salary, let alone getting a new computer that isn't already outdated).

 

I'm curious about the certification part, though. Yeah, sure, having a guarantee that drivers always work the same is nice, but how do they plan to enforce it? Does this mean it'll be outright illegal to release an OpenGL driver that isn't certified? I can see that being a massive issue for FOSS drivers (which does matter on Linux). Does anybody have exact details on what certification allows?

 

EDIT: should have checked more carefully

http://www.khronos.org/conformance/

 

OK, it's mostly a trademark issue (so e.g. Mesa probably still would be safe since it doesn't call itself OpenGL). It seems that FOSS implementations still would be able to go through the implementers program if they want to use the name (not the adopters one due to the fee).

Edited by Sik_the_hedgehog

Share this post


Link to post
Share on other sites

So, OpenGL 4.4 specs have been published, and AMD still doesn't have a working implementation of OpenGL 4.3. This is wonderful. rolleyes.gif

Well, AMD is much less of an issue than Intel, they (AMD) are actually pretty good nowadays. Intel is the real problem. They not only do not have a working implementation of OpenGL 4.0, but they also do not have a working implementation of OpenGL 3.0.

 

Which makes me wonder what this entire certification thing will be good for at all.

 

Intel will not pull functional 3.0 (let's not even imagine 4.4) drivers out of their magic hat, but Intel integrated GPUs are the main GPU in every El Cheapo computer, and in the major share of non-tablet computers anyway, too. And, outside the world of Android, they're pretty much omni-present in tablets as well.

 

Which will probably mean no more and no less than OpenGL will simply not be supported (or supported even worse as it is now) on a considerable share of hardware. Sorry for being pessimistic, but I just can't see Intel producing a quality 4.x driver and undergo certification any time soon. They'll just show everyone the middle finger, knowing their CPUs are sold anyway.

Share this post


Link to post
Share on other sites

 

So, OpenGL 4.4 specs have been published, and AMD still doesn't have a working implementation of OpenGL 4.3. This is wonderful. rolleyes.gif

Well, AMD is much less of an issue than Intel, they (AMD) are actually pretty good nowadays. Intel is the real problem. They not only do not have a working implementation of OpenGL 4.0, but they also do not have a working implementation of OpenGL 3.0.

 

Which makes me wonder what this entire certification thing will be good for at all.

 

Intel will not pull functional 3.0 (let's not even imagine 4.4) drivers out of their magic hat, but Intel integrated GPUs are the main GPU in every El Cheapo computer, and in the major share of non-tablet computers anyway, too. And, outside the world of Android, they're pretty much omni-present in tablets as well.

 

Which will probably mean no more and no less than OpenGL will simply not be supported (or supported even worse as it is now) on a considerable share of hardware. Sorry for being pessimistic, but I just can't see Intel producing a quality 4.x driver and undergo certification any time soon. They'll just show everyone the middle finger, knowing their CPUs are sold anyway.

 

 

 I really don't consider Intel to be that big of any issue. Their integrated graphics are in a completely different class compared to AMD and Nvidia's dedicated GPUs. I mean whats the real advantage to being able to enable the latest OpenGL 4 / DX11 level features in a game if its going to run at 5fps?

Edited by Chris_F

Share this post


Link to post
Share on other sites

 

Intel will not pull functional 3.0 (let's not even imagine 4.4) drivers out of their magic hat, but Intel integrated GPUs are the main GPU in every El Cheapo computer, and in the major share of non-tablet computers anyway, too. And, outside the world of Android, they're pretty much omni-present in tablets as well.

 

Which will probably mean no more and no less than OpenGL will simply not be supported (or supported even worse as it is now) on a considerable share of hardware. Sorry for being pessimistic, but I just can't see Intel producing a quality 4.x driver and undergo certification any time soon. They'll just show everyone the middle finger, knowing their CPUs are sold anyway.

 

 

I would be surprised if they added this certification if Intel haven't already said yes to it. What would be the point if it's still just AMD/Nvidia?

 

 

 

 I really don't consider Intel to be that big of any issue. Their integrated graphics are in a completely different class compared to AMD and Nvidia's dedicated GPUs. I mean whats the real advantage to being able to enable the latest OpenGL 4 / DX11 level features in a game if its going to run at 5fps?

 

 

That seems rather irrelevant in the context of conformance, where the point is that any features should behave the same, which is just as important if one only uses 2.0 functionality. AMD/Nvidia are already close enough, and the real advantage of the conformance tests would be when writing an application that doesn't require the beefiest hardware and being able to rely on it working the intended way on any device.

Share this post


Link to post
Share on other sites

Certification is just required for GL4.4+, so all that Intel (or AMD for that matter, should they be so inclined) have to do is freeze their implementation at a pre-4.4 level and hey-presto!  No need for certification and they can continue to ship driver bugs.

 

I wouldn't underestimate Intel, by the way.  Haswell is looking pretty good, is beating comparable parts from AMD, and in a couple more generations we may well see them emerging as a third serious player in the market.

Share this post


Link to post
Share on other sites

I wouldn't underestimate Intel, by the way.  Haswell is looking pretty good, is beating comparable parts from AMD, and in a couple more generations we may well see them emerging as a third serious player in the market.


Yeah, this.

Both in desktop and mobile the Intel machine has woken up and starting to push serious resources into the development; with AMD's CPU division sucking away the profits from graphics if Intel can keep up investment they could move into second place.

As for GL4.4; there isn't really a great deal to it.
From the headline features;

- Buffer Storage has mostly provoked arguements as to how useful it'll be (more so when the notes on the extension say that at least one of the bits might be ignored) - I'm pretty sure this also basically mimics D3D11's buffer controls

- Async Queries could be useful if you are doing anything which requires GPU output which would normally bounce thru a CPU buffer

- Shader Variable Layout, while intresting from a 'yay!' point of view is again basically a HLSL parity feature

- Multi-bind is a good addition but nothing earth shattering (and it's bizzare it wasn't about before... see D3D10)

- The 10-11-11 vertex format support is just... well, sane.. again, surprising it wasn't there before.

There are some intresting extensions about (sparse, bindless, draw parameters, variable group size(!), indirect parameters) but the core feels like a 'tidying up missing features vs D3D11' really.

Maybe GL4.5 will bring something new to the table in the core, we'll see, as D3D is basically stuck at D3D11 due to the enforcement of Win8.1 for D3D11.2 - OGL has basically a 3rd chance to try and become a viable option again.

Share this post


Link to post
Share on other sites

GPU hardware hasn't supported 3-component texture formats for a long time (aside from packed formats like DXT1).


If you ask GL to give you an RGB texture, on the GPU it will allocate an RGBA texture and pretend that the alpha channel doesn't exit...
 

 

Learn something new every day! Good to know this.. 

Share this post


Link to post
Share on other sites

Don't be like that, its getting there! tongue.png

 

"Getting there" isn't good enough.  GL4.3 has been specified for the past year, AMD are a member of the standards body that specified it, they should have had a full GL4.3 driver long ago.

Share this post


Link to post
Share on other sites

They should put more effort into streamlining the API again, and I'm not sure why we don't have a single state vector yet, neither why samplers are not solely shader side for example.

It would also be nice to be able to generate and submit a command buffer sequence easily. (Create it once, resubmit it as many times as you want, sorta like a copy/paste operation.)

 

How many ways do we need to specify a typed multi-dimensional array ?

BufferData, BufferStorage, TextureImage*, TexStorage*... That's way too many...

 

The API is at last giving us access to hardware features that have been available for years now, but the API isn't making the jump I'd like to see and change once and for all into OpenGL Lean & Mean, a promise from 2002 for OpenGL 2.0... (Long before 3.0/Long Peaks)

Edited by Ingenu

Share this post


Link to post
Share on other sites

What I don't get about query buffers is that for most query objects (including occlusion and timer, the most interesting ones) it says that at most one query can be active at a time.

 

In other words, you can now read many queries into a buffer object to avoid stalls and to avoid a round-trip to the CPU, but you can still only run one query at a time. Which, frankly, isn't so much different.

 

The only useful application is really transform feedback and/or geometry shader (where more than one query at a time can be active).

Share this post


Link to post
Share on other sites

Has anyone tried to implement the sparse textures? I've placed glTexParameteri(GL_TEXTURE_3D, GL_TEXTURE_SPARSE_ARB, GL_TRUE) into my code and it compiles fine but there does not seem to be anything shader specific written in the specs (similar to the AMD versions where you use sparseTexture(sampler, coord)).

Share this post


Link to post
Share on other sites
Ah, yes, that omission... it took me a while to spot it as well (mostly because I couldn't believe it WAS missing); but yes, as it stands ARB_sparse_texture lacks the GLSL extension for shader -> cpu feedback loops.

While annoying this doesn't render the extension useless it just means you have to manage things via corser CPU side controls rather than using a shader feedback loop (which, to be honest, for a streaming solution you'll want anyway so no foul there really).

Part of me wonders if this omission is due to an NV or Intel GPU weakness where their current hardware can do the virtual texturing bit just fine but can't do the feedback loop; probably because it pretty much requires a writable buffer to be bound to any pipeline stage to be completely viable for all situations something AMD can do but it seems NV can't/won't expose on some/all of their hardware (see D3D11.1 'uav on all pipeline stages' issue for NV)... and god knows about Intel.

Truth be told however this extension, and the more powerful AMD varient get more intresting once the tiled resource extension comes into play; I don't have a link to the pdf handy but basically you'll be able to reserve a buffer (say 128meg) and then allocate out of that tile sized resources to your sparse textures rather than relying on the driver's best guess as it currently stands. (edit: and now I have the link to hand! Hardware Virtual Textures has the details.)

Combine sparse, memory controls and bindless and you've got one hell of a powerful set of features going forward. Edited by phantom

Share this post


Link to post
Share on other sites

Part of me wonders if this omission is due to an NV or Intel GPU weakness where their current hardware can do the virtual texturing bit just fine but can't do the feedback loop;

Indeed, Nvidia supports the general virtual memory framework but not the shader feedback. Hence DX11.2 having two tiers for tiled resources, with the second tier having the shader extensions.

Edited by MJP

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By reenigne
      For those that don't know me. I am the individual who's two videos are listed here under setup for https://wiki.libsdl.org/Tutorials
      I also run grhmedia.com where I host the projects and code for the tutorials I have online.
      Recently, I received a notice from youtube they will be implementing their new policy in protecting video content as of which I won't be monetized till I meat there required number of viewers and views each month.

      Frankly, I'm pretty sick of youtube. I put up a video and someone else learns from it and puts up another video and because of the way youtube does their placement they end up with more views.
      Even guys that clearly post false information such as one individual who said GLEW 2.0 was broken because he didn't know how to compile it. He in short didn't know how to modify the script he used because he didn't understand make files and how the requirements of the compiler and library changes needed some different flags.

      At the end of the month when they implement this I will take down the content and host on my own server purely and it will be a paid system and or patreon. 

      I get my videos may be a bit dry, I generally figure people are there to learn how to do something and I rather not waste their time. 
      I used to also help people for free even those coming from the other videos. That won't be the case any more. I used to just take anyone emails and work with them my email is posted on the site.

      I don't expect to get the required number of subscribers in that time or increased views. Even if I did well it wouldn't take care of each reoccurring month.
      I figure this is simpler and I don't plan on putting some sort of exorbitant fee for a monthly subscription or the like.
      I was thinking on the lines of a few dollars 1,2, and 3 and the larger subscription gets you assistance with the content in the tutorials if needed that month.
      Maybe another fee if it is related but not directly in the content. 
      The fees would serve to cut down on the number of people who ask for help and maybe encourage some of the people to actually pay attention to what is said rather than do their own thing. That actually turns out to be 90% of the issues. I spent 6 hours helping one individual last week I must have asked him 20 times did you do exactly like I said in the video even pointed directly to the section. When he finally sent me a copy of the what he entered I knew then and there he had not. I circled it and I pointed out that wasn't what I said to do in the video. I didn't tell him what was wrong and how I knew that way he would go back and actually follow what it said to do. He then reported it worked. Yea, no kidding following directions works. But hey isn't alone and well its part of the learning process.

      So the point of this isn't to be a gripe session. I'm just looking for a bit of feed back. Do you think the fees are unreasonable?
      Should I keep the youtube channel and do just the fees with patreon or do you think locking the content to my site and require a subscription is an idea.

      I'm just looking at the fact it is unrealistic to think youtube/google will actually get stuff right or that youtube viewers will actually bother to start looking for more accurate videos. 
    • By Balma Alparisi
      i got error 1282 in my code.
      sf::ContextSettings settings; settings.majorVersion = 4; settings.minorVersion = 5; settings.attributeFlags = settings.Core; sf::Window window; window.create(sf::VideoMode(1600, 900), "Texture Unit Rectangle", sf::Style::Close, settings); window.setActive(true); window.setVerticalSyncEnabled(true); glewInit(); GLuint shaderProgram = createShaderProgram("FX/Rectangle.vss", "FX/Rectangle.fss"); float vertex[] = { -0.5f,0.5f,0.0f, 0.0f,0.0f, -0.5f,-0.5f,0.0f, 0.0f,1.0f, 0.5f,0.5f,0.0f, 1.0f,0.0f, 0.5,-0.5f,0.0f, 1.0f,1.0f, }; GLuint indices[] = { 0,1,2, 1,2,3, }; GLuint vao; glGenVertexArrays(1, &vao); glBindVertexArray(vao); GLuint vbo; glGenBuffers(1, &vbo); glBindBuffer(GL_ARRAY_BUFFER, vbo); glBufferData(GL_ARRAY_BUFFER, sizeof(vertex), vertex, GL_STATIC_DRAW); GLuint ebo; glGenBuffers(1, &ebo); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ebo); glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(indices), indices,GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, false, sizeof(float) * 5, (void*)0); glEnableVertexAttribArray(0); glVertexAttribPointer(1, 2, GL_FLOAT, false, sizeof(float) * 5, (void*)(sizeof(float) * 3)); glEnableVertexAttribArray(1); GLuint texture[2]; glGenTextures(2, texture); glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageOne = new sf::Image; bool isImageOneLoaded = imageOne->loadFromFile("Texture/container.jpg"); if (isImageOneLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageOne->getSize().x, imageOne->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageOne->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageOne; glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageTwo = new sf::Image; bool isImageTwoLoaded = imageTwo->loadFromFile("Texture/awesomeface.png"); if (isImageTwoLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageTwo->getSize().x, imageTwo->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageTwo->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageTwo; glUniform1i(glGetUniformLocation(shaderProgram, "inTextureOne"), 0); glUniform1i(glGetUniformLocation(shaderProgram, "inTextureTwo"), 1); GLenum error = glGetError(); std::cout << error << std::endl; sf::Event event; bool isRunning = true; while (isRunning) { while (window.pollEvent(event)) { if (event.type == event.Closed) { isRunning = false; } } glClear(GL_COLOR_BUFFER_BIT); if (isImageOneLoaded && isImageTwoLoaded) { glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glUseProgram(shaderProgram); } glBindVertexArray(vao); glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, nullptr); glBindVertexArray(0); window.display(); } glDeleteVertexArrays(1, &vao); glDeleteBuffers(1, &vbo); glDeleteBuffers(1, &ebo); glDeleteProgram(shaderProgram); glDeleteTextures(2,texture); return 0; } and this is the vertex shader
      #version 450 core layout(location=0) in vec3 inPos; layout(location=1) in vec2 inTexCoord; out vec2 TexCoord; void main() { gl_Position=vec4(inPos,1.0); TexCoord=inTexCoord; } and the fragment shader
      #version 450 core in vec2 TexCoord; uniform sampler2D inTextureOne; uniform sampler2D inTextureTwo; out vec4 FragmentColor; void main() { FragmentColor=mix(texture(inTextureOne,TexCoord),texture(inTextureTwo,TexCoord),0.2); } I was expecting awesomeface.png on top of container.jpg

    • By khawk
      We've just released all of the source code for the NeHe OpenGL lessons on our Github page at https://github.com/gamedev-net/nehe-opengl. code - 43 total platforms, configurations, and languages are included.
      Now operated by GameDev.net, NeHe is located at http://nehe.gamedev.net where it has been a valuable resource for developers wanting to learn OpenGL and graphics programming.

      View full story
    • By TheChubu
      The Khronos™ Group, an open consortium of leading hardware and software companies, announces from the SIGGRAPH 2017 Conference the immediate public availability of the OpenGL® 4.6 specification. OpenGL 4.6 integrates the functionality of numerous ARB and EXT extensions created by Khronos members AMD, Intel, and NVIDIA into core, including the capability to ingest SPIR-V™ shaders.
      SPIR-V is a Khronos-defined standard intermediate language for parallel compute and graphics, which enables content creators to simplify their shader authoring and management pipelines while providing significant source shading language flexibility. OpenGL 4.6 adds support for ingesting SPIR-V shaders to the core specification, guaranteeing that SPIR-V shaders will be widely supported by OpenGL implementations.
      OpenGL 4.6 adds the functionality of these ARB extensions to OpenGL’s core specification:
      GL_ARB_gl_spirv and GL_ARB_spirv_extensions to standardize SPIR-V support for OpenGL GL_ARB_indirect_parameters and GL_ARB_shader_draw_parameters for reducing the CPU overhead associated with rendering batches of geometry GL_ARB_pipeline_statistics_query and GL_ARB_transform_feedback_overflow_querystandardize OpenGL support for features available in Direct3D GL_ARB_texture_filter_anisotropic (based on GL_EXT_texture_filter_anisotropic) brings previously IP encumbered functionality into OpenGL to improve the visual quality of textured scenes GL_ARB_polygon_offset_clamp (based on GL_EXT_polygon_offset_clamp) suppresses a common visual artifact known as a “light leak” associated with rendering shadows GL_ARB_shader_atomic_counter_ops and GL_ARB_shader_group_vote add shader intrinsics supported by all desktop vendors to improve functionality and performance GL_KHR_no_error reduces driver overhead by allowing the application to indicate that it expects error-free operation so errors need not be generated In addition to the above features being added to OpenGL 4.6, the following are being released as extensions:
      GL_KHR_parallel_shader_compile allows applications to launch multiple shader compile threads to improve shader compile throughput WGL_ARB_create_context_no_error and GXL_ARB_create_context_no_error allow no error contexts to be created with WGL or GLX that support the GL_KHR_no_error extension “I’m proud to announce OpenGL 4.6 as the most feature-rich version of OpenGL yet. We've brought together the most popular, widely-supported extensions into a new core specification to give OpenGL developers and end users an improved baseline feature set. This includes resolving previous intellectual property roadblocks to bringing anisotropic texture filtering and polygon offset clamping into the core specification to enable widespread implementation and usage,” said Piers Daniell, chair of the OpenGL Working Group at Khronos. “The OpenGL working group will continue to respond to market needs and work with GPU vendors to ensure OpenGL remains a viable and evolving graphics API for all its customers and users across many vital industries.“
      The OpenGL 4.6 specification can be found at https://khronos.org/registry/OpenGL/index_gl.php. The GLSL to SPIR-V compiler glslang has been updated with GLSL 4.60 support, and can be found at https://github.com/KhronosGroup/glslang.
      Sophisticated graphics applications will also benefit from a set of newly released extensions for both OpenGL and OpenGL ES to enable interoperability with Vulkan and Direct3D. These extensions are named:
      GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_memory_object_win32 GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_semaphore_win32 GL_EXT_win32_keyed_mutex They can be found at: https://khronos.org/registry/OpenGL/index_gl.php
      Industry Support for OpenGL 4.6
      “With OpenGL 4.6 our customers have an improved set of core features available on our full range of OpenGL 4.x capable GPUs. These features provide improved rendering quality, performance and functionality. As the graphics industry’s most popular API, we fully support OpenGL and will continue to work closely with the Khronos Group on the development of new OpenGL specifications and extensions for our customers. NVIDIA has released beta OpenGL 4.6 drivers today at https://developer.nvidia.com/opengl-driver so developers can use these new features right away,” said Bob Pette, vice president, Professional Graphics at NVIDIA.
      "OpenGL 4.6 will be the first OpenGL release where conformant open source implementations based on the Mesa project will be deliverable in a reasonable timeframe after release. The open sourcing of the OpenGL conformance test suite and ongoing work between Khronos and X.org will also allow for non-vendor led open source implementations to achieve conformance in the near future," said David Airlie, senior principal engineer at Red Hat, and developer on Mesa/X.org projects.

      View full story
    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
  • Advertisement