• Advertisement

# OpenGL Drawing 3D "manually"...

This topic is 4805 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 all I'm currently working on a project (along with a few others) to draw some 3D stuff, which will hopefully turn into a rendering engine eventually. I searched for a bit on these forums, and google with no luck. What i would like to do is draw 3D points on the 2D screen, with a depth buffer. I understand that the camera is a 4x4 matrix, along with the point, and i know all rotation matricies ant stuff like that. What is getting me is, given the projection (is it a matrix? in OGL it's gluPerspective(50,1,1,100) ) then how to I get the 2D point on the screen and how far away it is for Depth?? I've worked with OpenGL for a while now, with a little DirectX, and i think that will help me.. Thanks for anything (sorry if this topic has been brought up before) ~zix~ [Edited by - zix99 on November 22, 2004 3:05:15 PM]

#### Share this post

##### Share on other sites
Advertisement
Yes, projection is a matrix. The DX SDK help files detail how the projection matrix is created.

What then occurs is: vertexposition (with an assumed w of 1...[x,y,z,1]) * world * view * projection.

The resulting vector is the divided by W. Now you're in clip space. In DX thats -1<x<1, -1<y<1, and 0<z<1. I think I've seen somewhere that in OpenGL z goes from -1 to 1 too... it's a full cube.

From here, you discard and/or clip the triangles to fit within those boundaries. You can also do this before dividing by W, where -w<x<w, -w<y<w, etc..

Then you apply viewport scaling. Basically scale and offset the x and y into pixel coordinates. For a 640x480 screen that would be x*320+320 and y*240+240. Then, rasterize your result.

#### Share this post

##### Share on other sites
Any good tutorials that might show exaclty how to do this (I'll look into the DirectX SDK)?
Including drawing triangles/texturing triangles...

Thanks again
~zix~

#### Share this post

##### Share on other sites
Yeah, look up the D3DXMatrixPerspectiveLH function in the DirectX SDK help file, it shows you exactly what the perspective matrix looks like.

It's this:

w       0       0               00       h       0               00       0       zf/(zf-zn)      10       0       -zn*zf/(zf-zn)  0where:h is the view space height. It is calculated from h = cot(fovY/2);w is the view space width. It is calculated from w = h * aspect   (where aspect = screenWidth/screenHeight)zf = farthest visible distance, zn = nearest visible distance

So, this works with homogenous coordinates. for a vertex:

  [x, y, z, 1]

you get the following: output vertex

  [x*w, y*h, (z-zn)*zf / (zf-zn), z]

which becomes (After the homogenous divide by w)

  [x*w/z, y*h/z, (1-zn/z)*zf / (zf-zn), 1]

In the case of D3D's matrices, you end up with x and y in the range [-1, 1] and z in the range [0, 1], 1 being farthest from the camera (the z-far plane) and 0 being nearest (z-near plane).

Hope that helps :)

#### Share this post

##### Share on other sites
Drillan, thank you very much for that response, quite helpful. Now, sense I have one subject down, all that's left is drawing filled triangles (dont forget i'm using depth so if it is translated to 2D then drawn, i still need depth). Also texturing, but this can be covered later if needed.

One question for namethatnobodyelsetook
Quote:
 What then occurs is: vertexposition (with an assumed w of 1...[x,y,z,1]) * world * view * projection.

So, if I am correct it would look something like (if camera was at 0,0,0 and point was at 5,5,0):
1  0  0  5                 1  0  0  0    w  0  0  00  1  0  5   *  WORLD?  *  0  1  0  0  * 0  h  0  00  0  1  0                 0  0  1  0    0  0  zf/(zf-zn)  10  0  0  1                 0  0  0  1    0  0  -zn*zf/(zf-zn)  0

I figure rotating the camera is simply just multiplying the viewport coordinates by the rotation matrix?

Thanks again
~zix~

PS: I rated u guys up.. but it's not doing anything.. is the rating system broken??

#### Share this post

##### Share on other sites
To draw a triangle, start by drawing the lines of the triangle. Look into Bresenham's line algorithm for details. When you draw the lines to the screen you only need to keep track of the smallest x value, and the greatest x value of the line.

So you could keep two array's of min x and max x.

MIN X MAX X
[0] [0]
[1] [1]
. .
. .
[480] [480]

The array would be the height of the screen, then just iterate through the array and connect the lines horizontally. In array position [0] you could have a value of 10, and array 2 position [0] you could have a value of 100, that means that left most outer edge of the traingle 0 pixels down on the screen is at 10, and the right most edge of the triangle 0 pixels down is at 100. A simple for loop from 10 to 100, filling in each pixel with an interpolated color or a sampled UV coord will give you a colored/textured triangle.

- Hope thats clear.

#### Share this post

##### Share on other sites
Quote:
 Original post by zix99So, if I am correct it would look something like (if camera was at 0,0,0 and point was at 5,5,0):1 0 0 5 1 0 0 0 w 0 0 00 1 0 5 * WORLD? * 0 1 0 0 * 0 h 0 00 0 1 0 0 0 1 0 0 0 zf/(zf-zn) 10 0 0 1 0 0 0 1 0 0 -zn*zf/(zf-zn) 0I figure rotating the camera is simply just multiplying the viewport coordinates by the rotation matrix?

The correct order of operations is world*view*proj.

I don't understand what you mean by point was at 5,5,0 do you mean the look at point for the camera? I'm not sure what you mean but, for camera, every thing is inverted, because the world is transformed to move the camera back to 0,0,0. So if the camera was translated 5,5,0 forward the matrix would have -5,-5,0 in the translation portions.

#### Share this post

##### Share on other sites
Maybe this is clearer?
(5,5,0)                    (0,0,0)Vertex Pos      World      Camera        Projection1  0  0  5                 1  0  0  0    w  0  0  00  1  0  5   *  WORLD?  *  0  1  0  0  * 0  h  0  00  0  1  0                 0  0  1  0    0  0  zf/(zf-zn)  10  0  0  1                 0  0  0  1    0  0  -zn*zf/(zf-zn)  0

According to namethatnooneelsetook it is
Quote:
 vertexposition (with an assumed w of 1...[x,y,z,1]) * world * view * projection.

And i'm a little confused on what the world matrix vs view matrix is. I'm guessing the view matrix is the same as the camera (inverted); in that case what is the world?

Thanks
~Zix

PS: Thanks for the triangle algo, once you have the 3 positions of the triangle, then you simple interpoliate the UV coordinates and draw accordingly (relativly simple).. correct? I'll have to do some thinking on this (along with the aspect of depth buffer), but i think i may have it.

#### Share this post

##### Share on other sites
OpenGL doesn't necessarily have a world, you have a modelview matrix which is both world and view together (I could be wrong, I've never used OpenGL).

In DirectX the World matrix is the matrix that transforms a vertex to world space. ie: It positions and rotates a mesh.

The view matrix is the inverse of the camera's world matrix. If your camera was at 1,2,3, the inverse of that would be a translation matrix of -1,-2,-3. Instead of actually moving a camera through the world, the world is dragged (and rotated) to the camera.

So, lets say we have a vertex at the origin. Lets say our mesh is at 0,0,10. Lets say the camera is at 0,0,2.

vertex pos = 0,0,0
*worldmatrix = 0,0,10
*viewmatrix = 0,0,8
*projection = ...

#### Share this post

##### Share on other sites
Thanks everyone.. I'll test all these ideas out and let you know how it goes.

I'll also rate you guys up as soon as it lets me.
EDIT: It just wont let me rate Drillan... is it because he's a GDNet member? o well, i guess i'll report to bugs

~zix~

#### Share this post

##### Share on other sites
Quote:
 Original post by NamethatnobodyelsetookWhat then occurs is: vertexposition (with an assumed w of 1...[x,y,z,1]) * world * view * projection.The resulting vector is the divided by W. Now you're in clip space. In DX thats -1

I have a question on this. What happens if W is now 0? I've been working on a project like this for a class at school and I am having that problem. Where I have a unit pyramid with the top point at (0, .5, 0, 1) and after I do all my transformations and go to do perspective division W is now 0 so it screws it all up. BTW, I have my world axes with X->right, Z->up, Y->in (because our teacher wants it that way).

So maybe I'm doing something wrong with the transformations. I don't know. But if you could just answer that question for me I'd be grateful. :)

#### Share this post

##### Share on other sites
If your w is 0 when it comes to perspective division, you probably screwed up your transformation matrix. IIRC w should come out equal to the distance between the point and the camera...

For the most part it seems like you can treat w as a binary flag. If it's 1, translations will be applied to the vector. If it's 0, they won't.

Quote:
 Original post by zix99I'll also rate you guys up as soon as it lets me.EDIT: It just wont let me rate Drillan... is it because he's a GDNet member? o well, i guess i'll report to bugs
Don't worry, your rating's been recorded. It just doesn't have any effect at the moment because you and he both have the same score. I, however, can rate him up, and change his score. *rates*

#### Share this post

##### Share on other sites
Quote:
 I have a question on this. What happens if W is now 0? I've been working on a project like this for a class at school and I am having that problem. Where I have a unit pyramid with the top point at (0, .5, 0, 1) and after I do all my transformations and go to do perspective division W is now 0 so it screws it all up. BTW, I have my world axes with X->right, Z->up, Y->in (because our teacher wants it that way).So maybe I'm doing something wrong with the transformations. I don't know. But if you could just answer that question for me I'd be grateful. :)

W=0 implies that the point is 'at infinity'. If you imagine a line passing through your eye (from in front of you, through your head and out the back), the perspective transform kind of turns space inside out (it's hard to visualize).

After the perspective transform you are in clip space and it is perfectly possible for primitives to wrap around infinity and come back (e.g. a line like above). You MUST clip to your view frustum (which is actually a 'parallelpiped' or box in clip space). After clipping you will only get W=0 for a point if you don't have an offset in your z (in other words Zn=0).

#### Share this post

##### Share on other sites
Yeah, w=0 implies that the point is at infinity. Another way to look at it is that, if w=0, the x,y, and z coordinates are the direction TO that point (so if the coordinate is [0,1,0,0] then the point is at infinity down the +Y axis).

You definitely shouldn't end up with w = 0 after the perspective matrix is applied.

Really, you want to treat your vectors as a 4x1 matrix, so it'd be:

(5,5,0)                    (0,0,0)Vertex Pos      World      Camera        Projection                           1  0  0  0    w  0  0  05  5  0  1   *  WORLD   *  0  1  0  0  * 0  h  0  0                           0  0  1  0    0  0  zf/(zf-zn)  1                           0  0  0  1    0  0  -zn*zf/(zf-zn)  0

The transform you're doing won't come out correctly because a vector is not the same thing as a transform matrix :)

Hope that helps!

#### Share this post

##### Share on other sites
Thanks all again for the information.. and good thing i kept up on this otherwise i would've never treated the vector as a 4x1 matrix, i would've treated it as a 4x4.

Thanks again Drillan, seems you have some background in this.

And thanks superpig for taking care of the rating

~zix~

#### Share this post

##### Share on other sites
No, you can perfectly well have W=0 because after the perspective transform W is proportional to the original Z coordinate.

In fact, taking Drillians example:

(I'll discard the World and camera transform, presume we're in camera space and this point happens to fall at Z=0)

v' = v * P

x' = (5 * w) + (5 * 0) + (0 * 0) + (1 * 0)
y' = (5 * 0) + (5 * h) + (0 * 0) + (1 * 0)
z' = (5 * 0) + (5 * 0) + (0 * ...) + (-zn*zf/(zf-zn))
w' = (5 * 0) + (5 * 0) + (0 * 1) + (1 * 0)

So this point does have W=0!

The point is that this point will be clipped away since z' < Zn.

#### Share this post

##### Share on other sites
Ah! You're correct. Forgot about the ol' "z = 0" case. Yeah, because the perspective is, at its most basic level, a divide by z (which is why you set the w coordinate to z: because in order to get the normalized coordinate you divide by the w parameter [x y z w] -> [x/w, y/w, z/w, 1]). But when z = 0, the perspective divide becomes a divide by zero, which effectively puts the coordinate at infinity in post-perspective space.

But JuNC is right, that point gets clipped away due to the near Z value, so in practice you should never actually see this.

Good catch!

#### Share this post

##### Share on other sites
This seems interesting. I might give it a try and program my own software renderer.

My only question is, what does the projected point look like? Are the coordinates from (-1,-1) to (1,1), where (0,0) is the center of the screen, and outside that range is outside of the screen?

And whats the standard algorithm for, say, a color filled polygon? You project the 3 vertices, draw the edges to find min and max values in terms of rows, and then fill each row?

#### Share this post

##### Share on other sites
Quote:
 Original post by Max_PayneMy only question is, what does the projected point look like? Are the coordinates from (-1,-1) to (1,1), where (0,0) is the center of the screen, and outside that range is outside of the screen?

To do simple project to -1,-1 to 1,1 you use this matrix.

1 0 0 0
0 1 0 0
0 0 1 1/D
0 0 0 0

The X, Y, Z get multiplied by the 1 across the diagnal, and the Z get's multipled by the recipical of D. So the Z value is stored in the W value of the vertex you multiply it by. This is useful when you actually do projection and divide (x,y,z,w) by w, to get (x/w, y/w, z/w, 1) you can discard the z and w and get your projected coordinates (x/w, y/w).

Those numbers are in-dependent on your viewport or field of view. The viewport is factored into the w(x) and h(y) values of the above matrix. In directX the width can be calculated using field of view or viewport. If you want to depend on the view port you would do this.

w = 2 * z-near / ViewportWidth;
h = 2 * z-near / ViewportHeight;

so your matrix is
w 0 0 0
0 h 0 0
0 0 1 1
0 0 0 0

Also, you probally are going to want to factor z in for the near and far plane, to do that use
Q = Zfar / ( zfar - znear )

to get the matrix
w 0 0 0
0 h 0 0
0 0 q 1
0 0 0 0

That will account for a viewport that can be set rather then the standard -1,-1, to 1,1.

Quote:
 And whats the standard algorithm for, say, a color filled polygon? You project the 3 vertices, draw the edges to find min and max values in terms of rows, and then fill each row?

Read my post above, but basically what you said sums it up.

#### Share this post

##### Share on other sites

• Advertisement
• Advertisement
• ### Popular Tags

• Advertisement

• 10
• 11
• 9
• 16
• 19
• ### 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.

• 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