Sign in to follow this  

OpenGL frustrum culling.. what in the world am I doing wrong??

Recommended Posts

All right, I have wasted sooo much time trying to figure out what in the world I do wrong: I jsut wat to to simple frustum culling, using Oriented boxes: with the notation of openGL in mind: I first define an eye_frustrum with the same parameters that one passes to glFrustum, i.e. left,right,top,bottom,near and far. because I have been getting depserate I have computed the corners of the frustum as follows:
  m_left_top_near=vec3(proj.m_left, proj.m_top, proj.m_near);
  m_left_bottom_near=vec3(proj.m_left, proj.m_bottom, proj.m_near);
  m_right_top_near=vec3(proj.m_right, proj.m_top, proj.m_near);
  m_right_bottom_near=vec3(proj.m_right, proj.m_bottom, proj.m_near);


  m_middle=0.5f*vec3(proj.m_left+proj.m_right, proj.m_top+proj.m_bottom, proj.m_near+proj.m_far)

I know that for Frustum culling you really do not need the corners, but I have them so I can draw the frustum more easily, I then get the planes with:
//set the left plane:
normal=VectorCrossProduct(m_left_top_far - m_left_top_near, m_left_bottom_far- m_left_bottom_near);
m_planes[left_plane].Set(normal, m_left_top_far);

  //set the right plane:
normal=VectorCrossProduct(m_right_bottom_far - m_right_bottom_near, m_right_top_far - m_right_top_near);
m_planes[right_plane].Set(normal, m_right_bottom_far);

//set the top plane:
normal=VectorCrossProduct(m_right_top_far - m_right_top_near, m_left_top_far - m_left_top_near);
m_planes[top_plane].Set(normal, m_right_top_far);

//set the bottom plane:
normal=VectorCrossProduct(m_left_bottom_far - m_left_bottom_near, m_right_bottom_far - m_right_bottom_near);
m_planes[bottom_plane].Set(normal, m_left_bottom_far);

//set the near plane:
normal=VectorCrossProduct(m_right_bottom_near - m_left_bottom_near, m_left_top_near-m_left_bottom_near);
m_planes[near_plane].Set(normal, m_right_bottom_near);

//set the far plane:
normal=VectorCrossProduct(m_left_top_far-m_left_bottom_far, m_right_bottom_far - m_left_bottom_far);
m_planes[far_plane].Set(normal, m_right_bottom_far);

and then I get my frustum in world co-ordinates with:
#define lazy(x) do { x=GenericCameraClass::world_transformPt_eye(eye_matrix_world, eye.x); } while(0)




the relavent goo for the Plane code is:
class Plane

  void Set(const vec3 &normal, const vec3 pt) 

  void Set(const vec3 &normal, float v)
    float mag;



 bool Intersects(const GeneralCube &cube) const;


//(in another file)

bool Plane::Intersects(const GeneralCube &cube) const
  float p,v;
  int i;
  bool retval,retval2;
  v=dot(, m_normal);
  p=abs(cube.radiuses(0)*dot(m_normal,cube.axis(0)) ) + 
    abs(cube.radiuses(1)*dot(m_normal,cube.axis(1)) ) + 
    abs(cube.radiuses(2)*dot(m_normal,cube.axis(2)) );
  LogStream(FrustumLog,"p=" << p << " v=" << v << " m_value=" << m_value << "\n");
  //paranoia: the above test should be enough, but we'll go
  //ahead and check all vertices anyways.
  for(retval2=false, i=0;i<8;++i)
      retval2=retval2 || (dot(m_normal, cube.Vertex(i))>=m_value);	
  return retval;

and I am using <cmath> so abs does do the right thing here... now at this point, if I just make a frustum, it works correctly, i.e. I correctly detect when a frustrum and cube intersect (actually when no plane of the frustum is entrirly on one side)... my cubes are in world coordinates always, and the code for GenericCameraClass::world_transformPt_eye is:
static vec3 world_transformPt_eye(const float4x4 &matrix, vec3 in) 
    in-=vec3(matrix.GLElement(0,3), matrix.GLElement(1,3), matrix.GLElement(2,3));
    return in*matrix;

the relavent code for the matrix stuff is:
class float4x4
  GLfloat data[16];
  GLfloat *operator[](int i) 
    ASSERT(0<=i && i<4);
    return data + 4*i;
  const GLfloat *operator[](int i) const
    ASSERT(0<=i && i<4);
    return data + 4*i;

  GLfloat &GLElement(int i, int j)
    ASSERT(0<=i && i<4);
    ASSERT(0<=j && j<4);

    return data[4*j+i];

 //more stuff....


inline vec3 operator*(const float4x4 &matrix, const vec3 &in)
  vec3 out;
  int i,j;


  return out;

and I pass the matrix to openGL for modelview stuff with (here camera is a const float4x4*) and state is state stuff for a mesh where m_matrixState is the matrix that goes from model co-ordinatres to eye-cooridnates.

so what in the world am I doing wrong in my Frustum code? as of now meshes get culled if the viewer is not "inside" the meshes bounding box... [Edited by - kRogue on December 12, 2006 2:09:54 PM]

Share this post

Link to post
Share on other sites
just one more note, reading the internet and man pages gives different anwers to what glFrustum does:

accorind to openGL specs from

M=| 2n/(r-l) 0 (r+l)/(r-l) 0 |
| 0 2n/(t-b) (t+b)/(t-b) 0 |
| 0 0 -(f+n)/(f-n) -2fn/(f-n) |
| 0 0 -1 0 |

where as apples website ( gives

M=| 2n/(r-l) 0 (r+l)/(r-l) 0 |
| 0 2n/(t-b) (t+b)/(t-b) 0 |
| 0 0 +(f+n)/(f-n) -2fn/(f-n) |
| 0 0 -1 0 |

another place ( gives

M=| 2n/(r-l) 0 (r+l)/(r-l) 0 |
| 0 2n/(t-b) (t+b)/(t-b) 0 |
| 0 0 +(f+n)/(f-n) +2fn/(f-n) |
| 0 0 -1 0 |

and I would not be surprised if the 3rd row has 4 different answers depending on which man page one reads! Note: on my hardware (nVidia GeForce6600GT, Linux OS) I get the answer from openGL's specification.

note, this means something interesting about the planes (which I should ahve realized):
1) z_eye should be negative in order to see it with -far<=z_eye<=-near

at any rate, this made me realize that I was creating the eye_frustum incorrectly, the corner points should be:

//set the corners
// some horible truth, the near and far need
// to be negated to get an accurate picture of
// the frustum since the frustum is
// -far <= z_eye <= -near
// thus we use -near instead of near, and -far instead of far.
// note that to do this is the same as just changing
// m_*_near.z() to -near, and letting m_*_far=ratio*m_*_near;

m_left_top_near=vec3(proj.m_left, proj.m_top, -proj.m_near);
m_left_bottom_near=vec3(proj.m_left, proj.m_bottom, -proj.m_near);
m_right_top_near=vec3(proj.m_right, proj.m_top, -proj.m_near);
m_right_bottom_near=vec3(proj.m_right, proj.m_bottom, -proj.m_near);


m_middle=0.5f*vec3(proj.m_left+proj.m_right, proj.m_top+proj.m_bottom, -proj.m_near-proj.m_far);

and there all the VectorCrossProducts in figuring out the normals to the plains need to be negated (or just change VectorCrossProduct(a,b) to VectorCrossProduct(b,a) )....

I put these posts up, because not only is some of the online docs wrong for glFrustum, but I wasted more than a day realzing this "negation" issue...

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  

  • 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