# OpenGL Unprojection of points / Homogenous clip coords make me perplex

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

## Recommended Posts

Hi,

i have been spending a lot of time to track a bug in my projection pipeline. I am implementing ray picking for my diploma thesis - actually just a UI thing
I did not plan to waste so much time on it.

I used two different methods to unproject:
1) Place an imageplane in front of the camera and shoot a ray
2) Invert the projection matrix multiply and homogenize

In both cases i observed that the generated rays were a little of and missed the scene parts they were suppossed to hit slightly. Just because I ran out of ideas
I translated the ray origin to (0,0, -1) and suddenly it worked perfectly.

I could ignore that little glitch, but it leaves me with a bad feeling as I do not understand what happens behind the curtains. The ray origin should be (0,0,0) - right ?

As I ran into the problem twice, I suppose I did fail to understand all aspects of homogenous clip coordinates. I will post my projection matrices and maybe you guys could
give me some advice what I am doing wrong - This is really starting to frustrate me.

My viewport to NDC matrix (row vectors):

x: (1.0f / (width / 2.0f)), 0, 0 ,0)
y: (0, (1.0f / (height / 2.0f)), 0 ,0)
z: (0, 0, 1 ,0)
w:(-1.0f 1.0f 0 ,1)

My projection matrix: (symmetric frustum)

x: (near / right, 0 0 0)
y: (0 near/top 0 0)
z:(0, 0 (far + near)) / (far - near) 1) //Camera is looking in positive z, opposed to vanilla OpenGL
w(0, 0 -(2 * far * near) / (far - near) 1)

The inverse projection matrix (after [url="http://www.bookofhook.com/mousepick.pdf"]Mouse Ray Picking Explained[/url]):

x: (right / near, 0 0 0)
y: (0 top / near 0 0)
z: (0 0 0 (far - near) / (-(2*far*near))
w:(0 0 1 (far + near) / ( 2*far*near))

I am not sure the matrices will help, but maybe you got an idea what i might have forgot ?

The actual method (java) looks like this:
[CODE]
/*
* Returns a ray in eye space
*/
public Ray raycast(Point2 position) {
//Viewport to NDC
Point3 pickPoint = paintingSurface.normalise(new Point3(position, 0));

//NDC to eye coordinates
Point3 reprojectedPoint = inverseProjection.multiply(pickPoint);
reprojectedPoint.homogenousDivide();

Vector3 rayDir = reprojectedPoint.subtract(Point3.ZERO);
rayDir.normalize();

return new Ray(new Point3(0,0,-1), rayDir); /// :-(((((( Why???
}
[/CODE]

I would be glad if anybody could point out my error.

Thanks a lot,
Frederick

##### Share on other sites
[quote name='Frederick' timestamp='1300486104' post='4787717']
My projection matrix: (symmetric frustum)

x: (near / right, 0 0 0)
y: (0 near/top 0 0)
z:(0, 0 (far + near)) / (far - near) 1) //Camera is looking in positive z, opposed to vanilla OpenGL
w(0, 0 -(2 * far * near) / (far - near) 1)[/quote]I'm definitely not sure about this projection matrix. I'm pretty sure it wouldn't come from any perspective or orthographic projection. If you actually do mean for that, what sort of projection are you intending?

##### Share on other sites
Hi Geometrian,

thank you so much for pointing that out. Of course it was meant as a projection matrix - and it did the visual - kind of.

I took the matrix from [url="http://www.songho.ca/opengl/gl_projectionmatrix.html"]here[/url]
But I didn´t notice that the w coordinate of the translational part of this matrix is set to zero. I thought that w of the translational part must always be one. The w value
introduced the weird translation I had to fight with.

Maybe I have to rethink my whole approach concerning matrices. I learned from David Eberlys fine "Geometric Tools" that it is a good idea to distinct point and vectors.
And I distinct them per type. So I have a point and a vector class. Points w is always 1, Vector w is always 0. At least I thought so.
I had to relax this lately because the homogenous approach to perspective division demands w values different from zero or one.

My whole approach to matrices is somewhat broken now. Maybe I will rewrite them. My current approach looks like this:
[quote]
public class Matrix3 {

private Vector3 x, y, z;
private Point3 w;

[...]
}[/quote]

Up to now I liked it and thought it was elegant, but there are cases like projection when w actually is not a point.

Now i do something like:

[quote]matrix3.w().setW(0.0f) [/quote] which contradicts the statement that w is of type point3.

Maybe I have to abandon this approach. I also have never seen anybody do it like this - there might be a reason....

Thank you so much and extra pair of eyes can really do wonders sometimes - I was so stuck in my approach - I would have never noticed that glitch.

Frederick

• ### 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,
glUseProgram(program.get());
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?
glUseProgram(0);
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?

• My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:

• 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
Hello,
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 (http://natureofcode.com/book/chapter-6-autonomous-agents/) inspirate from another code (here: https://github.com/jyanar/Boids/tree/master/src) 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): https://github.com/pr033r/BachelorProject/tree/Optimalizing
Exe file (if you want to look) and models folder (for those who will download the sources):
http://leteckaposta.cz/367190436
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:
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