• Advertisement
Sign in to follow this  

OpenGL Does the OpenGL fixed function pipeline compute lighting in view-space?

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

[color=#000000][font=Arial,]Does the OpenGL fixed function pipeline compute lighting in view-space?[/font][/color]

[color=#000000][font=Arial,]If the answer is yes, then how does it cope with view transformations with non-uniform scale? Actually, how does it cope with view transformations incorporating [i]any[/i] scale at all?[/font][/color]

[color=#000000][font=Arial,]If this is true then scaling the view space will result in different light-to-vertex distances, meaning the lighting intensity for point-lights will change as the view matrix is scaled.[/font][/color]

[color=#000000][font=Arial,]Lighting in world-space would make the computed point-light intensity independent of view space scaling, but would require:[/font][/color]
[list]
[*]That an object-to-world matrix is supplied to the API (such as in DirectX, where the light positions are specified in world-space).
[*]That the API transform all geometry twice when drawing. Once by world*view*proj into clip space, and again by world, in order to compute lighting at the vertices in world space.
[/list]

[color=#000000][font=Arial,]I also posted this to stackoverflow, perhaps you want to answer it there too: [url="http://stackoverflow.com/questions/10830759/does-the-opengl-fixed-function-pipeline-compute-lighting-in-view-space"]http://stackoverflow...g-in-view-space[/url][/font][/color] Edited by infact

Share this post


Link to post
Share on other sites
Advertisement
It sounds like you aren't a OpenGL user.
GL doesn't have a view matrix and it doesn't have a world matrix. GL only has a modelview matrix.
GL transforms vertices by the modelview matrix to get eye space vertices. It also transform normals by the inverse transpose of the modelview matrix to get eye space normal vectors. Lighting is computed in eye space. In order to deal with non uniform scale, you can glEnable(GL_NORMALIZE). If you only have a uniform scale, you can glEnable(GL_RESCALE) which is "faster" than GL_NORMALIZE.

Of course, all of the above is relevant to the year 2002 and before. It's time to move to the world of shaders. Edited by V-man

Share this post


Link to post
Share on other sites
My question is not about the effect that the transformation has on the normals.

From the documentation I can see that OpenGL has a MODELVIEW matrix, which is a concatenation of the MODEL and VIEW matrices, so from that point of view OpenGL can support separate model and view matrices.

Now consider the difference between: distance(vertex*model - world_light) and distance(vertex*modelview - view_light).

Notice how the distance between the vertex and the light can change, potentially depending on the non-uniform scaling in the matrix. Edited by infact

Share this post


Link to post
Share on other sites
[quote name='infact' timestamp='1338463275' post='4944940']From the documentation I can see that OpenGL has a MODELVIEW matrix, which is a concatenation of the MODEL and VIEW matrices, so from that point of view OpenGL can support separate model and view matrices.[/quote]
From the point of view of OpenGL, there is only 1 matrix called the modelview matrix. Notice how "modelview" is composed of the words model and view. No, OpenGL doesn't support "separate model and view matrices". It is a single matrix.


[quote name='infact' timestamp='1338463275' post='4944940']
Now consider the difference between: distance(vertex*model - world_light) and distance(vertex*modelview - view_light).

Notice how the distance between the vertex and the light can change, potentially depending on the non-uniform scaling in the matrix.
[/quote]

You don't apply the same matrix to all your objects and all your lights.

Share this post


Link to post
Share on other sites
My point is that lighting in world space will be different to lighting in view space.

distance(vertex*view - light) != distance(vertex - light*view^-1)

this is clear if we let the light origin be 0,0,0, and consider a matrix with no translation, then we have that:

length(vertex*view) != length(vertex)

which is true

In other words, the transformation distorts the lighting

So I wonder why opengl does lighting in view space and not in world space.

Is it for the the sake of having a single modelview matrix instead of separate model and view matrices in the pipeline? Edited by infact

Share this post


Link to post
Share on other sites
as far as I know lighting is space independent. It should be the same for world, view, and tangent space.
The implementation might compute lighting in any of these spaces, but it must provide you with the variables and functions that you see in the specs, and it has to act accordingly.

Share this post


Link to post
Share on other sites
[quote name='infact' timestamp='1338478857' post='4945016']
My point is that lighting in world space will be different to lighting in view space.

distance(vertex*view - light) != distance(vertex - light*view^-1)

this is clear if we let the light origin be 0,0,0, and consider a matrix with no translation, then we have that:

length(vertex*view) != distance(vertex)

which is true

In other words, the transformation distorts the lighting

So I wonder why opengl does lighting in view space and not in world space.

Is it for the the sake of having a single modelview matrix instead of separate model and view matrices in the pipeline?
[/quote]
If view is a zero-translation matrix without scaling, then distance(vertex*view) == distance(vertex) and so lighting is the same in both spaces. If it incorporates scaling, then the distances will indeed be different, but it is only different from a conceptual quantity that doesn't exist in OpenGL. You can easily move the scaling from the view matrix into the model matrix instead to ensure that the view matrix is rotation only (assuming the given non-zero translation). You are basically comparing a result agains an intermetiate value that has no meaning in OpenGL.

Share this post


Link to post
Share on other sites
[quote name='infact' timestamp='1338478857' post='4945016']
My point is that lighting in world space will be different to lighting in view space.

distance(vertex*view - light) != distance(vertex - light*view^-1)

this is clear if we let the light origin be 0,0,0, and consider a matrix with no translation, then we have that:

length(vertex*view) != distance(vertex)

which is true

In other words, the transformation distorts the lighting

So I wonder why opengl does lighting in view space and not in world space.

Is it for the the sake of having a single modelview matrix instead of separate model and view matrices in the pipeline?
[/quote]

Ok, I see. I did a test and yes, there is a difference in distance depending on which space you are working in when there is scale applied.
It seems to be a problem for point lights and spot lights and when you need to use attenuation.

However, I don't see this as a problem for fixed function GL because fixed function GL doesn't do its lighting computation in object space.

But for someone who is using shaders, and let's say he wants to do bump mapping on certain objects and phong lighting on something else, the attenuation will appear different and he might wonder why. The bump mapped object would appear brighter.

Is the above correct? Can someone verify it? Edited by V-man

Share this post


Link to post
Share on other sites
yes lighting is not distorted. If you compute light intensity at several distances from light source and you place vertices at that distances from light source the intensity will be correct.

the only thing that is distorted is fog, and that's because fog is usually computed using Z-buffer values instead of distances of vertices from camera. NVIDIA made an extension for that (eye radial fog) but that's OT.

Maybe you should know that geometries are distorted by projection. Human eyes is a semisphere internally, while computer monitor is a flat surface (does anyone ever experimented stretched cubes near sides of frustum view? In the reality a cube will not be stretched even if at limits of vision range) so geometry projection is already a distortion from what you will see if you were for really in the game. But there is nothing you can do for that ^^.

That's why stereo-monitors aren't so good and some people complain about headhackes looking at 3D movies for more than several minutes.. There was also a study at Berkley sponsored by Samsung.

For shaders that's the same. If you want correct lighting you need to compute distance from camera in vertex shader and then feed fragment shader with the interpolated varying. you can't use Zbuffer value in shaders for that.

Most shaders based on Zbuffer values infact are doing some space correction (for example SSAO) Edited by DemonRad

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