Sign in to follow this  
CDProp

OpenGL Is there a trick to getting two-sided lighting to work?

Recommended Posts

I have some models that I have to use, which contain a lot of double-sided polygons. I want to enable double-sided lighting, so that the side facing the light looks lit, and the side facing away looks shadowed.

I'm enabling GL_LIGHT_MODEL_TWO_SIDE, but that doesn't seem to work. Just like before, both sides look lit/dark depending on where the front face is oriented with respect to the incoming light.

Is there some other setting that needs to be enabled as well?

I'm working with a complex scene graph, where each node has its own OpenGL state, and parent nodes can override child nodes, and all sorts of crazy crap like that. So, it's really difficult for me to verify that GL_LIGHT_MODEL_TWO_SIDE is indeed set at the time that the draw call is made. But, before I dig into that, I thought I'd just check real quick to make sure there isn't something simple that I'm missing.

If all else fails, I guess I'll just write my own shader. Bonus question: I know the FFP stuff was deprecated. Does that mean we'll lose access to all of those built-in uniforms like gl_Vertex, gl_Normal, gl_ModelViewMatrix and so on? I've always liked having access to those.

Share this post


Link to post
Share on other sites
Are your triangles wound properly? I've seen people before seem to think that they could have triangles wound incorrectly but enabling two sided lighting would solve their problems, but it doesn't.

All two sided lighting does is flip the normal when rendering the polygon backface. You should get the correct lighting if your normals are pointing correctly out of the front face of the polygon.

Is this the case in your situation? Sorry if I've misunderstood your question.

Quote:

Bonus question: I know the FFP stuff was deprecated. Does that mean we'll lose access to all of those built-in uniforms like gl_Vertex, gl_Normal, gl_ModelViewMatrix and so on? I've always liked having access to those.

Yep those are deprecated as well. You can still access them if you like via a compatibility profile, but I'd recommend just using your own matrices. You can't do a lot of shader techniques without access to separate model and view matrices, which you can't get via the built in matrices.

Share this post


Link to post
Share on other sites
Yeah, good point. I end up sending down my own matrices for those things anyway. Time to cut the FFP apron strings!

I'm pretty sure the winding order is okay. I haven't noticed any problems before. It's a very simple model. I think something else in the scene graph must be overriding the state that I'm setting, or something.

So, in OpenGL 3+, how does the vertex data get sent to the vertex shader? I know that DirectX 9 does it through vertex declarations that tie vertex data to the shader arguments. Does OpenGL use something similar?


Share this post


Link to post
Share on other sites
To send the vertex data (known as 'attributes'), you declare a variable in the shader, get its index with glGetAttribLocation, then use glVertexAttribPointer to specify the vbo data that maps to that input variable.

Are you using glLightModel to enable it? You're not trying to use glEnable are you? Are you checking for errors in your program?

I can't think of any other options that would need to be enabled.

Share this post


Link to post
Share on other sites
Ooh, that's a good question. I'm using an OpenSceneGraph function to set the mode, but I'm not sure if it's smart enough to detect which mode is being set and use the appropriate OpenGL call. I might be using a function that is reserved for glEnable-type calls only.

I'll check and see if they have something special in mind for glLightModel.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Partner Spotlight

  • Forum Statistics

    • Total Topics
      627639
    • Total Posts
      2978345
  • Similar Content

    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
    • By cebugdev
      hi guys, 
      are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
      Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic 
      let me know if you guys have recommendations.
      Thank you in advance!
    • By dud3
      How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below? 
      Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
      Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.
       
      References:
      Code: https://pastebin.com/Hcshj3FQ
      The video shows the difference between blender and my rotation:
       
    • By Defend
      I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
      My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
      * make lots of VAO/VBO pairs and flip through them to render different objects, or
      * make one big VBO and jump around its memory to render different objects. 
      I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
      If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?
       
    • By test opty
      Hello all,
       
      On my Windows 7 x64 machine I wrote the code below on VS 2017 and ran it.
      #include <glad/glad.h>  #include <GLFW/glfw3.h> #include <std_lib_facilities_4.h> using namespace std; void framebuffer_size_callback(GLFWwindow* window , int width, int height) {     glViewport(0, 0, width, height); } //****************************** void processInput(GLFWwindow* window) {     if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS)         glfwSetWindowShouldClose(window, true); } //********************************* int main() {     glfwInit();     glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);     glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);     glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);     //glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);     GLFWwindow* window = glfwCreateWindow(800, 600, "LearnOpenGL", nullptr, nullptr);     if (window == nullptr)     {         cout << "Failed to create GLFW window" << endl;         glfwTerminate();         return -1;     }     glfwMakeContextCurrent(window);     if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress))     {         cout << "Failed to initialize GLAD" << endl;         return -1;     }     glViewport(0, 0, 600, 480);     glfwSetFramebufferSizeCallback(window, framebuffer_size_callback);     glClearColor(0.2f, 0.3f, 0.3f, 1.0f);     glClear(GL_COLOR_BUFFER_BIT);     while (!glfwWindowShouldClose(window))     {         processInput(window);         glfwSwapBuffers(window);         glfwPollEvents();     }     glfwTerminate();     return 0; }  
      The result should be a fixed dark green-blueish color as the end of here. But the color of my window turns from black to green-blueish repeatedly in high speed! I thought it might be a problem with my Graphics card driver but I've updated it and it's: NVIDIA GeForce GTX 750 Ti.
      What is the problem and how to solve it please?
  • Popular Now