• Advertisement

Archived

This topic is now archived and is closed to further replies.

OpenGL gluLookAt - Cameras in OpenGL

This topic is 5685 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

I already had a little conversation about this in the For Beginners forum but this is NOT a double post, I swear! I like to describe my camera with vectors. In a raytracer I gave my camera 4 vectors and that worked great: one for location, one for direction, one for U vector of the camera plane and one for V vector of the camera plane. With that, I could move, roll, yaw, pitch, change x and y fov, and even skew the camera and get some alien effects. Now I'm busy with OpenGL and I'm having some difficulties with the camera. First I planned to move and rotate the world with glTranslatef and glRotatef, but because glRotatef used euclidiean angles it wasn't good for my camera (that uses a vector for the looking direction). So someone suggested that I should use gluLookAt and that looked perfect at first sight... until I tried it. I'm getting some unwanted results now: 1) I still use glTranslatef for the translation of the camera because gluLookAt did a little bit weird with it. It has problems with negative numbers appearantly, why is that? 2) It supports upx, upy and upz, but does it also support this for the horizontal direction? (I think this is a retorical question because appearantly it doesn't) 3) My biggest problem and concern is this: I'm completely confused with the coordinate system. The rotation works, and the translation with glTranslatef too but BAD, appearantly, the axes of translation rotate together with the camera direction and that's NOT what I want. I simply change the X position of the camera with 2 arrow keys, but if the camera is rotated, the camera translates along other directions than the X position. Why is that? I prefer to use ABSOLUTE world coordinates (I just thrust that more) for my camera so if I change the X direction, it always moves along that axis no matter how the camera is rotated. How do I do that? Thanks. EDIT: OMG! I found out that there's an even bigger problem! If I moved my camera far away from the scene I found out that the scene is rotating indeed, and not the camera How do I properly work with cameras in OGL? [edited by - Lode on July 28, 2002 9:45:02 AM]

Share this post


Link to post
Share on other sites
Advertisement
Go to gametutorials.com and look at their opengl camera tutorials. It looks like your main problem is using glTranslatef for the translation of the camera, which is stemming off a whole bunch of other problems.

Oh yeah:

quote:

2) It supports upx, upy and upz, but does it also support this for the horizontal direction? (I think this is a retorical question because appearantly it doesn't)



Think about it - gluLookAt calculates its horizontal vector from the up and eye vectors.

Heres something i whipped up in psp:



[edit] - when looking at that diagram, imagine the up vector going along the Y axis, the eye going down the z axis and the horizontal going along X. Its not a 2d diagram

[edited by - sark on July 28, 2002 5:29:45 PM]

Share this post


Link to post
Share on other sites
www.gametutorials.com
Mentioned already, but worth mentioning again.

Why do you need a horizontal vector? The up vector''s purpose is to tell what direction is up, by using that, you obviously know what way is right/left.

As for the camera not moving along the X axis, I suggest you do not use glRotatef on the camera. Possiblely on other objects, but not the camera. Use gametutorials rotations instead.

As for your edit, of course the scene moves. You have a flat, stationary moniter. What do you expect to move?

------------
aud.vze.com - The Audacious Engine <-- It''s not much, yet. But it''s mine... my own... my preciousssss...
MSN: nmaster42@hotmail.com, AIM: LockePick42, ICQ: 74128155

Share this post


Link to post
Share on other sites
Good point about the monitor :D

For the horizontal vector: well changing xfov and vfov seperatly can be handy sometimes, for example that looks just better sometimes when resizing a window to non 4:3 sizes. In case I WANT the scene to be stretched if I stretch the window namely. And the camera skewing is cool too for special effects but for that I would have to be able to make the horizontal and vertical vector not perpendicular.

/me checks gametutorials.com

[edited by - Lode on July 28, 2002 7:35:36 PM]

Share this post


Link to post
Share on other sites
Hmm, well that''s an interesting point. But that would require a much more complex function than gluLookAt to mess around with the screen like that.
Really, all gluLookAt does is ask for more logical information. Normally we don''t think "rotate head 45 on y, rotate head 25 on z" we think "look at object". It takes our version and turns it into glTranslate/glRotatef. And this is just to calculate where things are on screen. Not to do anything to the screen itself.

Perhaps there some tweaks you could do to the perspective/viewport functions instead.

------------
aud.vze.com - The Audacious Engine <-- It''s not much, yet. But it''s mine... my own... my preciousssss...
MSN: nmaster42@hotmail.com, AIM: LockePick42, ICQ: 74128155

Share this post


Link to post
Share on other sites

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement