• Advertisement
Sign in to follow this  

OpenGL Position Reconstruction from Depth in OpenGL

This topic is 2081 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

Hi Everybody,

I'm in a long journey of implementing deferred shading. I've got a clear idea of the algorithm, but have some troubles reconstructing object position. I've followed this article [url="http://mynameismjp.wordpress.com/2009/03/10/reconstructing-position-from-depth/"]http://mynameismjp.wordpress.com/2009/03/10/reconstructing-position-from-depth/[/url] but still easily get lots. There are too many uncertainties. So I want to go over it step by step and make that I did not make any mistakes in previous steps.


Storing the depth into a texture:

[CODE]
// Depth Pass Vertex Shader

varying float depth;
void main (void)
{
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;
vec4 pos = gl_ModelViewMatrix * gl_Vertex;
depth = pos.z;
}
[/CODE]

[CODE]
// Depth Pass Fragment Shader
varying float depth;
uniform float FarClipPlane;
void main (void)
{
float d = - depth / FarClipPlane;
gl_FragColor.r = d;
}
[/CODE]

My understanding of this is that I do store the liner depth value into the texture. Is that correct?

Thank you,
Ruben


Also, I'm easily getting lost when it gets to the perspective division. Can somebody suggest some article where i can learn about it.

Share this post


Link to post
Share on other sites
Advertisement
Yes, this is correct, but you should move the division into the vertex shader.
[CODE]
varying float depth;
uniform float FarClipPlane;
void main (void)
{
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;
vec4 pos = gl_ModelViewMatrix * gl_Vertex;
depth = -pos.z / FarClipPlane;
}

// Depth Pass Fragment Shader
varying float depth;
void main (void)
{
gl_FragColor.r = depth;
}
[/CODE]
And remember, that holding the depth in a single component of 8bit or 16bit will introduce artifacts.

Share this post


Link to post
Share on other sites
[quote name='rubenhak' timestamp='1336513950' post='4938494']
Hi Everybody,

I'm in a long journey of implementing deferred shading. I've got a clear idea of the algorithm, but have some troubles reconstructing object position. I've followed this article [url="http://mynameismjp.wordpress.com/2009/03/10/reconstructing-position-from-depth/"]http://mynameismjp.w...ion-from-depth/[/url] but still easily get lots. There are too many uncertainties. So I want to go over it step by step and make that I did not make any mistakes in previous steps.


Storing the depth into a texture:

[CODE]
// Depth Pass Vertex Shader

varying float depth;
void main (void)
{
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;
vec4 pos = gl_ModelViewMatrix * gl_Vertex;
depth = pos.z;
}
[/CODE]

[CODE]
// Depth Pass Fragment Shader
varying float depth;
uniform float FarClipPlane;
void main (void)
{
float d = - depth / FarClipPlane;
gl_FragColor.r = d;
}
[/CODE]

My understanding of this is that I do store the liner depth value into the texture. Is that correct?

Thank you,
Ruben


Also, I'm easily getting lost when it gets to the perspective division. Can somebody suggest some article where i can learn about it.
[/quote]

Ashaman73 is correct, however you seem to be having trouble with the theory itself.
before reading take a look at this:
http://mynameismjp.wordpress.com/2010/09/05/position-from-depth-3/
namely method #2

Ok so you store the depth like this:
[CODE]
[vertex shader]

varying float depth;
const float far_plane_distance = 1000.0f; //far plane is at -1000

[...]

//transform the input vertex to view (or eye) space
vec4 viewspace_position = modelview_matrix * input_vertex;

//this is not perspective division but scaling the depth value.
//initially you'd have depth values in the range [-near ... -far distance]
//but you have to linearize them, so that you can get more
//precision
//this is why you divide by the far plane distance
//and you divide by the negative one, so that you can
//check the result in the texture
depth = viewspace_position.z / -far_plane_distance;

[pixel shader]

varying float depth;
out vec4 out_depth;

[...]

//store the depth into the R channel of the texture
//assuming you chose a R16F or R31F format
out_depth.x = depth;

[/CODE]

and retrieve (decode) the depth like this:
[CODE]
[vertex shader]

varying vec4 viewspace_position;
varying vec2 texture_coordinates;

[...]

//store the view space position of the far plane
//this gets interpolated as you could see in the mjp drawing
viewspace_position = modelview_matrix * input_vertex;
texture_coordinates = input_texture_coordinates;

[pixel shader]

varying vec4 viewspace_position;
varying vec2 texture_coordinates;
uniform sampler2D depth_texture;
const float far_plane_distance = 1000.0f;

[...]

//sample depth from the texture's R channel
//this will be in range [0 ... 1]
float linear_depth = texture(depth_texture, texture_coordinates).x;

//you have to construct the view vector at the extrapolated viewspace position
//and scale it by the far / z, but this is unnecessary if you use the far plane as the input viewspace position
//since the division will give you 1
//the z coordinate will be the far distance (negative, since we're in viewspace)
vec3 view_vector = vec3(viewspace_position.xy * (-far_plane_distance / viewspace_position.z), -far_plane_distance);

//scaling the view vector with the linear depth will give the true viewspace position
vec3 reconstructed_viewspace_position = view_vector * linear_depth;

[/CODE]

hope this helped :) I had trouble with reconstructing position so search for it on gamedev.

Share this post


Link to post
Share on other sites
[quote name='Ashaman73' timestamp='1336550949' post='4938605']
Yes, this is correct, but you should move the division into the vertex shader.
[/quote]
Could you please explain what would be the difference of doing that in a vertex vs pixel shaders. Except the performance difference, aren't the numbers supposed to be same?

[quote name='Ashaman73' timestamp='1336550949' post='4938605']
And remember, that holding the depth in a single component of 8bit or 16bit will introduce artifacts.
[/quote]
I will try to encode it into 3 or 4 8bit components. You already gave the idea how to do that in another thread.

Share this post


Link to post
Share on other sites
[quote name='Yours3!f' timestamp='1336564479' post='4938643']
Ashaman73 is correct, however you seem to be having trouble with the theory itself.
before reading take a look at this:
[url="http://mynameismjp.wordpress.com/2010/09/05/position-from-depth-3/"]http://mynameismjp.w...n-from-depth-3/[/url]
namely method #2

Ok so you store the depth like this:

hope this helped [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] I had trouble with reconstructing position so search for it on gamedev.
[/quote]

I've read those lots of times but its very hard to understand the entire thing at once. I need to do it step-by-step.
Yours3!f, in one of the methods in the article frustum corner positions are used to reconstruct the position. I guess
it was used for world space position reconstruction, and you're reconstructing into view space, right?

So, if I go with the same approach, how should I perform lighting calculation? What would be the positions
of the camera and lights. Also regarding the normals, should that be translated? My understand is that in
view space:
[CODE]
camera_position_view_space = [0, 0, 0];
light_position_view_space = view_matrix * light_position_world_space;
light_direction_view_space = view_matrix * light_direction_world_space;
normal_view_space = normalize(view_matrix * normal_world_space);
[/CODE]

Ashaman73, Yours3!f, you guys help me a lot with this! I need some time to digest it.

Share this post


Link to post
Share on other sites
[quote name='rubenhak' timestamp='1336585651' post='4938714']
[quote name='Yours3!f' timestamp='1336564479' post='4938643']
Ashaman73 is correct, however you seem to be having trouble with the theory itself.
before reading take a look at this:
[url="http://mynameismjp.wordpress.com/2010/09/05/position-from-depth-3/"]http://mynameismjp.w...n-from-depth-3/[/url]
namely method #2

Ok so you store the depth like this:

hope this helped [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] I had trouble with reconstructing position so search for it on gamedev.
[/quote]

I've read those lots of times but its very hard to understand the entire thing at once. I need to do it step-by-step.
Yours3!f, in one of the methods in the article frustum corner positions are used to reconstruct the position. I guess
it was used for world space position reconstruction, and you're reconstructing into view space, right?

So, if I go with the same approach, how should I perform lighting calculation? What would be the positions
of the camera and lights. Also regarding the normals, should that be translated? My understand is that in
view space:
[CODE]
camera_position_view_space = [0, 0, 0];
light_position_view_space = view_matrix * light_position_world_space;
light_direction_view_space = view_matrix * light_direction_world_space;
normal_view_space = normalize(view_matrix * normal_world_space);
[/CODE]

Ashaman73, Yours3!f, you guys help me a lot with this! I need some time to digest it.
[/quote]

yep I describe the frustum corner method. I made it work in view space, but mjp describes a world space method as well. (so I guess the frustum one doesn't work in worldspace)
The lighting calculation is independent from what space you're using. Or at least I've seen lighting in world space, view space, tangent space... The basic thing is that you have to be consistent. If you're performing lighting in view space then you need to transform everything into view space. Normals, position, light position are the needed parameters. You should also read the lighthouse3d articles about lighting. If you wanna go the deferred way then I think viewspace suits your needs best.
To you viewspace, you just have to export your meshes to object space. The you can use your modelview matrix to transform them instantly into view space, and then the projection matrix to transform them to projection space.

for the normals you need to use a so called "normal matrix". This matrix is either the upper left 3x3 part of your view matrix, or the transpose of the inverse of your modelview matrix. You probably want to do this on the cpu side. In glsl:
[CODE]
mat3 normal_matrix_1 = mat3(view_matrix);

mat3 normal_matrix_2 = mat3(transpose(inverse(modelview_matrix)));
[/CODE] Edited by Yours3!f

Share this post


Link to post
Share on other sites
[quote name='Yours3!f' timestamp='1336662686' post='4939004']
yep I describe the frustum corner method. I made it work in view space, but mjp describes a world space method as well. (so I guess the frustum one doesn't work in worldspace)
[/quote]
OMG!! I didn't know those were your articles! Those are awesome! I honestly take my hat off for you!

Just want to confirm with you that with your method#2 I'd not need to deal with frustum corners, right? Multiplication of view_vector and linear_depth would give me reconstructed position in the view space.

Also, could you suggest some article where I can learn more about view/projection spaces in order to get a better idea how it works and why is the depth projected into [-far, -near] range.

Thank you!
Ruben

Share this post


Link to post
Share on other sites
[quote name='rubenhak' timestamp='1336669784' post='4939048']
[quote name='Yours3!f' timestamp='1336662686' post='4939004']
yep I describe the frustum corner method. I made it work in view space, but mjp describes a world space method as well. (so I guess the frustum one doesn't work in worldspace)
[/quote]
OMG!! I didn't know those were your articles! Those are awesome! I honestly take my hat off for you!

Just want to confirm with you that with your method#2 I'd not need to deal with frustum corners, right? Multiplication of view_vector and linear_depth would give me reconstructed position in the view space.

Also, could you suggest some article where I can learn more about view/projection spaces in order to get a better idea how it works and why is the depth projected into [-far, -near] range.

Thank you!
Ruben
[/quote]

ummm... I think you misunderstood me. That is not my article. I just implemented it. That article belongs to MJP: [url="http://www.gamedev.net/user/118414-mjp/"]http://www.gamedev.n...ser/118414-mjp/[/url]

you DO have to deal with it. That is the basis of the reconstruction. If you read the mjp article #3 (back in the habit) then you'll understand it. View vector is actually constructed from the coordinates of the far plane of the view frustum, that were interpolated along the whole screen.

just a couple of articles:
[url="http://www.songho.ca/opengl/gl_transform.html"]http://www.songho.ca..._transform.html[/url]
[url="http://www.songho.ca/opengl/gl_projectionmatrix.html"]http://www.songho.ca...tionmatrix.html[/url]
[url="http://www.songho.ca/math/homogeneous/homogeneous.html"]http://www.songho.ca...omogeneous.html[/url]
[url="http://www.glprogramming.com/red/chapter03.html"]http://www.glprogram.../chapter03.html[/url]
[url="http://www.glprogramming.com/red/"]http://www.glprogramming.com/red/[/url] ---> this is a whole book (although it is for OGL 1.1, some parts are still relevant like the article above)

this is an awesome book about the maths behind all this:
[url="http://www.amazon.com/Primer-Graphics-Development-Wordware-Library/dp/1556229119"]http://www.amazon.co...y/dp/1556229119[/url]
despite it describes maths in a left-handed coordinate system, I'm sure that after reading this you'll be able to apply it in the OpenGL world, the right-handed cooridnate system. Edited by Yours3!f

Share this post


Link to post
Share on other sites
Yours3!f, thank you so much for this! I really appreciate.
I need few days to digest and try it out. I will get back to this thread with my results!

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