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


OpenGL Replicating the OpenGL lighting equation

Recommended Posts

Monder    993
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
FReY    424
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
FReY    424
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
Monder    993
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
Monder    993

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

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now