Sign in to follow this  
jeroenb

OpenGL Strange behaviour [solved]

Recommended Posts

jeroenb    282
I am working on a project, where I noticed some strange flipping with the default opengl backface culling. On the image you can see what I mean (it is not the clearest picture). This picture contains a lot of boxes (all generated the same way, including per vertex normals). At the center of the image suddenly the front of the box isn't visible anymore but only the backside. During rotation, this 'swap' moves with the camera (I use the fixed pipeline). I have no clue what is going on here :s I have set up opengl just as normal. [Edited by - jeroenb on November 30, 2005 7:28:27 AM]

Share this post


Link to post
Share on other sites
Kwak    220
Seams to me like not all the normals are pointing the right way.
The direction (perpendicular to the face of the box) may be right, but the normals have to point to the outside of the boxes.

Share this post


Link to post
Share on other sites
jeroenb    282
I drawed a red line around the area where the strange behaviour can be seen best. The left box shows the correct faces, while the box to the right of it looks like to use an entirely different winding order. Odd thing is that all those boxes are generated the same, only thing I do is rotating them around the z-axis (the normals are calculated and averaged, thus not perpendicular to the face, after the rotations).

But I will have yet another look at the winding order/normals etc to see what is wrong.

Thanks for the replies!

ps. ignore the red dot, that has nothing to do with the problem :)

Share this post


Link to post
Share on other sites
OrangyTang    1298
Quote:
Original post by Kwak
Seams to me like not all the normals are pointing the right way.
The direction (perpendicular to the face of the box) may be right, but the normals have to point to the outside of the boxes.

Normals are not used for face culling, only vertex winding order is.

OP: Thats a slightly odd problem you've got there. :S Are you perhaps doing any mirroring or other fliping via the modelview matrix? Negative scales/mirrors will reverse the winding order and you'll have to change the cull face. Other than that the only thing I can suggest is to turn off face culling to check that that really is the problem.

Share this post


Link to post
Share on other sites
DJHoy    378
Quote:
Original post by OrangyTang
Normals are not used for face culling, only vertex winding order is.


Yeah - my first guess would be the vertex winding order... make sure the vertices are all orderde counter-clockwise (or clockwise) and set the openGL backface culling state approprately (unforuntately, I can't remember the call off the top of my head...)



Share this post


Link to post
Share on other sites
LilBudyWizer    491
Certainly looks like the winding order got reversed by mirroring. Particularly those gaps between boxes since they occur right at the position that you transition from drawing correctly to drawing incorrectly. That seems to be the plane of the front face of the structure on the platform to the top right suggesting that might be a coordinate plane of the object.

Share this post


Link to post
Share on other sites
jeroenb    282
I also forgot to mention that I use a modified JOGL for rendering (I made it use an FBO instead of a PBuffer for offscreen rendering) on the java platform :s.

I quadruple checked the winding order and finally got the idea to do a translate instead of a gluLookAt and that seemed to solve the problem. I do wonder though why it goes wrong when I use gluLookAt.

When I use fill mode with T&L lighting, it still looks completely wrong. I have a point light at position <0,0,0>, thus inside the geometry tunnel. When I look normally the geometry is lit, but when I rotate the geometry 180 degrees it is not. Strange is also that the geometry on the outside is also lit :s.

Share this post


Link to post
Share on other sites
jeroenb    282
--removed original message--

After player some more with it, the same problems arise with the pbuffer. Also is does not seem to be affected with changing gluLookAt to a translate (luckily). So, I am still at the same point as before. Guess I have to display normals to see how these are.

[Edited by - jeroenb on November 30, 2005 5:45:52 AM]

Share this post


Link to post
Share on other sites
jeroenb    282
I use an ATI mobile X300.

But this strange problem is solved. I again checked the given geometry, which I now noticed was the problem. The data with a negative Z had an incorrect winding order, which caused these troubles. I solved it with some swapping, if z was negative.

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 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.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
  • Popular Now