Sign in to follow this  

OpenGL Calculating frustum planes from arbitrary position/rotation [FIXED]

This topic is 4831 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi all, I have a Viewer class, which represents some entity capable of seeing things within my program's world. I'm trying to add some functions to calculate and perform tests on a viewer's frustum. Each viewer has its own information like fov, near/far plane distance, and aspect ratio. I've almost got everything working the way I want it, however some weird things happen: * I've checked all the values, but the frustum appears pointing out of the viewer's back, rather than in front. * The shape of the frustum appears to change as the viewer rotates about the Y (up) axis. I'm using OpenGL, however I am working in a coordinate system where the positive direction of the Z axis points into the screen, rather than out. This might be messing up some of the transformations... I calculate the frustum planes as follows: * Define the frustum planes in camera space. * Use OpenGL to do some transformations to bring camera space to world space. * Extract the matrix, and premultiply the 4-dimensional frustum vectors by it. * Normalise. To render the frustum, I'm finding the corners of the frustum by testing the intersection of 3 of the frustum planes, e.g. to get the near-top-left corner, I find the coordinates of intersection of the near, top, and left frustum planes. Like I say, it nearly works! But not quite. Perhaps some frustum-gurus have some advice for me? I've examined the plane normals, and they are most definitely correct in all the cases I've tried. I think it might be the D values that are messing up. Here's the frustum-plane calculating code: Few things to note: * e is calculated as 1 / tan(fovX), where fovX is the horizontal fov. * aspect is 0.75, in most cases. * One of the rotation lines is rot[1] - 90 rather than rot[1] because of the way I want my angles to point. This works.
// Precalculate frustum planes, from the viewer's position and orientation.
void Viewer::updateFrustumPlanes()
	// In camera coordinate space, the planes are easy to specify.
	// They are stored in the order near, far, left, right, bottom, top.
	float f[6][4];
	vec4Set(f[0], 0, 0, 1, near);
	vec4Set(f[1], 0, 0, -1, -far);
	vec4Set(f[2], e, 0, 1, 0);
	vec4Set(f[3], -e, 0, 1, 0);
	vec4Set(f[4], 0, e, aspect, 0);
	vec4Set(f[5], 0, -e, aspect, 0);
	// Now we must transform the planes from camera space to world space.
	// Perform the transformations.
	glRotatef(rot[0],         1.0f, 0.0f, 0.0f);
	glRotatef(rot[1] - 90.0f, 0.0f, 1.0f, 0.0f);
	glRotatef(rot[2],         0.0f, 0.0f, 1.0f);
	glTranslatef(-pos[0], -pos[1], -pos[2]);
	// Store the current matrix.
	float m[16];
	// Treating each plane as a 4-dimensional vector, transform each one by
	// the matrix we just saved to get the planes' coordinates in world space.
	for (int i = 0; i < 6; ++i)
		frustum[i][0] =
			m[0] * f[i][0] + m[1] * f[i][1] + m[2] * f[i][2] + m[3] * f[i][3];
		frustum[i][1] =
			m[4] * f[i][0] + m[5] * f[i][1] + m[6] * f[i][2] + m[7] * f[i][3];
		frustum[i][2] =
			m[8] * f[i][0] + m[9] * f[i][1] + m[10] * f[i][2] + m[11] * f[i][3];
		frustum[i][3] =
			m[12] * f[i][0] + m[13] * f[i][1] + m[14] * f[i][2] + m[15] * f[i][3];
	// Normalise the vectors.
	for (int i = 0; i < 6; ++i)

Oh, I also posted this to flipcode too. Hope that kind of cross-posting doesn't offend anybody :). [Edited by - smidge on October 25, 2004 11:16:41 AM]

Share this post

Link to post
Share on other sites
Ok, I'm lazy so I didn't read the whole message, from the topic I think you want that :

Extracting View Frustum Planes from the Camera matrix.

Share this post

Link to post
Share on other sites
Original post by Ingenu
Ok, I'm lazy so I didn't read the whole message, from the topic I think you want that :

Extracting View Frustum Planes from the Camera matrix.

Yes, that's not quite what I'm after - that article deals with extracting frustum planes from the existing projection matrix; however, I'm working with arbitrary camera coordinates and orientation, and don't want to have to alter the projection matrix each time I calculate something.

But not to worry, I fixed it the problem:


vec4Set(f[0], 0, 0, 1, near);
vec4Set(f[1], 0, 0, -1, -far);

.. should have been this:

vec4Set(f[0], 0, 0, 1, -near);
vec4Set(f[1], 0, 0, -1, far);

(silly mistake)

And the problem with the frustum changing shape, I noticed, made the d values of the top and bottom plane scale incorrectly with the other d values (in fact, they scaled at a ratio the same as the aspect ratio).

Normalising the f plane normals before transforming fixed that. All working nicely now.

Share this post

Link to post
Share on other sites

This topic is 4831 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

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 xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
    • By Jonathan2006
      My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:
      // This works quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); quat quaternion2 = GEMultiplyQuaternions(quaternion1, GEQuaternionFromAngleRadians(angleRadiansVector2)); quat quaternion3 = GEMultiplyQuaternions(quaternion2, GEQuaternionFromAngleRadians(angleRadiansVector3)); glMultMatrixf(GEMat4FromQuaternion(quaternion3).array); // The first two work fine but not the third. Why? quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); vec3 vector1 = GETransformQuaternionAndVector(quaternion1, angularVelocity1); quat quaternion2 = GEQuaternionFromAngleRadians(angleRadiansVector2); vec3 vector2 = GETransformQuaternionAndVector(quaternion2, angularVelocity2); // This doesn't work //quat quaternion3 = GEQuaternionFromAngleRadians(angleRadiansVector3); //vec3 vector3 = GETransformQuaternionAndVector(quaternion3, angularVelocity3); vec3 angleVelocity = GEAddVectors(vector1, vector2); // Does not work: vec3 angleVelocity = GEAddVectors(vector1, GEAddVectors(vector2, vector3)); static vec3 angleRadiansVector; vec3 angularAcceleration = GESetVector(0.0, 0.0, 0.0); // Sending it through one angular velocity later in my motion engine angleVelocity = GEAddVectors(angleVelocity, GEMultiplyVectorAndScalar(angularAcceleration, timeStep)); angleRadiansVector = GEAddVectors(angleRadiansVector, GEMultiplyVectorAndScalar(angleVelocity, timeStep)); glMultMatrixf(GEMat4FromEulerAngle(angleRadiansVector).array); Also how do I combine multiple angularAcceleration variables? Is there an easier way to transform the angular values?
    • By dpadam450
      I have this code below in both my vertex and fragment shader, however when I request glGetUniformLocation("Lights[0].diffuse") or "Lights[0].attenuation", it returns -1. It will only give me a valid uniform location if I actually use the diffuse/attenuation variables in the VERTEX shader. Because I use position in the vertex shader, it always returns a valid uniform location. I've read that I can share uniforms across both vertex and fragment, but I'm confused what this is even compiling to if this is the case.
      #define NUM_LIGHTS 2
      struct Light
          vec3 position;
          vec3 diffuse;
          float attenuation;
      uniform Light Lights[NUM_LIGHTS];
    • By pr033r
      I have a Bachelor project on topic "Implenet 3D Boid's algorithm in OpenGL". All OpenGL issues works fine for me, all rendering etc. But when I started implement the boid's algorithm it was getting worse and worse. I read article ( inspirate from another code (here: but it still doesn't work like in tutorials and videos. For example the main problem: when I apply Cohesion (one of three main laws of boids) it makes some "cycling knot". Second, when some flock touch to another it scary change the coordination or respawn in origin (x: 0, y:0. z:0). Just some streng things. 
      I followed many tutorials, change a try everything but it isn't so smooth, without lags like in another videos. I really need your help. 
      My code (optimalizing branch):
      Exe file (if you want to look) and models folder (for those who will download the sources):
      Thanks for any help...

    • By Andrija
      I am currently trying to implement shadow mapping into my project , but although i can render my depth map to the screen and it looks okay , when i sample it with shadowCoords there is no shadow.
      Here is my light space matrix calculation
      mat4x4 lightViewMatrix; vec3 sun_pos = {SUN_OFFSET * the_sun->direction[0], SUN_OFFSET * the_sun->direction[1], SUN_OFFSET * the_sun->direction[2]}; mat4x4_look_at(lightViewMatrix,sun_pos,player->pos,up); mat4x4_mul(lightSpaceMatrix,lightProjMatrix,lightViewMatrix); I will tweak the values for the size and frustum of the shadow map, but for now i just want to draw shadows around the player position
      the_sun->direction is a normalized vector so i multiply it by a constant to get the position.
      player->pos is the camera position in world space
      the light projection matrix is calculated like this:
      mat4x4_ortho(lightProjMatrix,-SHADOW_FAR,SHADOW_FAR,-SHADOW_FAR,SHADOW_FAR,NEAR,SHADOW_FAR); Shadow vertex shader:
      uniform mat4 light_space_matrix; void main() { gl_Position = light_space_matrix * transfMatrix * vec4(position, 1.0f); } Shadow fragment shader:
      out float fragDepth; void main() { fragDepth = gl_FragCoord.z; } I am using deferred rendering so i have all my world positions in the g_positions buffer
      My shadow calculation in the deferred fragment shader:
      float get_shadow_fac(vec4 light_space_pos) { vec3 shadow_coords = / light_space_pos.w; shadow_coords = shadow_coords * 0.5 + 0.5; float closest_depth = texture(shadow_map, shadow_coords.xy).r; float current_depth = shadow_coords.z; float shadow_fac = 1.0; if(closest_depth < current_depth) shadow_fac = 0.5; return shadow_fac; } I call the function like this:
      get_shadow_fac(light_space_matrix * vec4(position,1.0)); Where position is the value i got from sampling the g_position buffer
      Here is my depth texture (i know it will produce low quality shadows but i just want to get it working for now):
      sorry because of the compression , the black smudges are trees ...
      EDIT: Depth texture attachment:
  • Popular Now