Sign in to follow this  
floatingwoods

OpenGL GL_SPOT_EXPONENT and GL_SPOT_CUTOFF not working on Mac OSX

Recommended Posts

floatingwoods    364
Hello,

I have a cross-platform application that was first running on Windows. I ported it to Mac (using the Qt framework) and kept all the OpenGL routines same. Everything works as expected on Mac now, except for the spotlights.

It seems as if the command

glLighti(GL_LIGHT0+activeLightCounter,GL_SPOT_EXPONENT,spotExponentValue);

has no effect at all (i.e. behaves as with a spotExponent of 0 (default)). I tried values between 0 and 128, but nothing changes.

Additionally, following command

glLightf(GL_LIGHT0+activeLightCounter,GL_SPOT_CUTOFF,spotCutoffValue);

behaves strangely on Mac OSX: varying the value between 0 and 90, it seems that the visible cutoff is always around 10-20 degrees or so, and instantly goes to 180 degrees when I specify a value of 90!

This is very odd to me. Would someone have a clue? I need to mention that this happens on all tested Mac machine types (3) and OS versions (leopard, snow leopard and lion).

Is it possible that on Mac there are different default openGl settings? And if yes, which of those might influence the spotlights? (everything else appears same as on Windows).

Thanks for any insight

Share this post


Link to post
Share on other sites
V-man    813
Spot lights behave as point lights so fr their position, make sure that you provide a valid xyzw position. By that, I'm means that w should always be 1.0.
The direction of the spotlight, I don't remember if it was xyz or xyzw. If it takes a w, then w must be set to 0.0.

I'm not a Mac programmer but I know that they have a mailing list, in case you need to let them know about the bug you found.

Share this post


Link to post
Share on other sites
floatingwoods    364
Thanks for the reply V-man.

I could fix my problem, I guess there is a bug in the Mac implementation. Following is what I noticed (Mac only):

- with a spot cutoff of 90, the spot exponent cannot be changed (i.e. appears to be 0)

- glLighti(GL_LIGHT0,GL_SPOT_EXPONENT,spotExponent); doesn't work

- glLightf(GL_LIGHT0,GL_SPOT_EXPONENT,float(spotExponent)); works, but only if the spot cutoff is lower than 90 (see point 1)

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  

  • 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++.
      Question:
      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