This topic is now archived and is closed to further replies.


OpenGL Replicating the OpenGL lighting equation

Recommended Posts

In my 3D engine I''m planning to offer several lighting options. In one of them OpenGL will do the lighting and in another I do it manually by setting vertex colours before sending all the data off to OpenGL. Now as I want these two lighting methods to look the same I tried to clone the OpenGL lighting equation for my manual method. However when performing lighting using the two methods the manual one looks about twice as bright as the OpenGL one. I''m fairly sure the manual calculations that set the vertex colours individually are the same as the OpenGL ones, though mine do not include attenuation, I have set GL_CONSTANT_ATTENUATION set to 1.0 and GL_LINEAR_ATTENUATION and GL_QUADRATIC_ATTENUATION set to 0.0 for the light. Are there any gotchas I should watch out for that may be causing the difference between the two lighting methods? For example does OpenGL do anything to the colour array before applying lighting?

Share this post

Link to post
Share on other sites
are you taking into account materials at all? Default material reflectance for ambient lights is (0.2, 0.2, 0.2, 1.0) and default material reflectance for directional lights is (0.8, 0.8, 0.8, 1.0) so these may be adjusting your colours when using OpenGL lighting.

edit: typo!

[edited by - FReY on January 5, 2004 4:25:39 AM]

Share this post

Link to post
Share on other sites
After a quick google search I found the following in a .pdf assignment paper, get it from here:

The OpenGL equation for lighting is:

Vertex color = (material emission) + (global ambient)*(material ambient) +
Sigma(1/( k1+ k2*d + k3*d^2)) * [(light ambient)*(material ambient) + (max{L.N, 0})*(light
diffuse)*(material diffuse) + (max{H.N,0})^n *(light specular)*(material specular) ]

where H is your half vector for specular lighting and n is your specular power (or shininess in this case). d seems to be the distance of your vertex from the light and k1,k2,k3 are attenuation factors. I think the sigma is there for all the possible lights in the scene.

So if you''ve implemented this equation exactly then I have no idea of what the problem is. Maybe you could get clues from reading Chapter 5 of the Red book.

Share this post

Link to post
Share on other sites
Well when setting all the light colours to 0 apart from the diffuse colour which I set to 0.5, 0.5, 0.5, 1.0 (RGBA) my implementation gives an unevenly lit model (which is what it should be for diffuse light) but OpenGL gives an evenly lit model. I've set GL_LIGHT_MODEL_LOCAL_AMBIENT to 0.0, 0.0, 0.0, 1.0 so ambient light can't be affecting it. And it won't be a driver bug as I'm using the latest NVidia drivers.

Is there any specific order you have to specify parameters in and enable lights? For example do you have to specify light parameters before enabling the light?

[edited by - Monder on January 5, 2004 10:57:09 AM]

Share this post

Link to post
Share on other sites

Found the problem I was specifying a directional light, not a point light, I thought 1.0 as the W coord of the light position specified a point light and 0.0 was directional, but it''s the other way round. Ahh well thanks for the help guys.

Share this post

Link to post
Share on other sites

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • 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. 
  • Popular Now