Sign in to follow this  
mpledge52

OpenGL Camera help

Recommended Posts

mpledge52    138
I'm trying to make a camera which will allow me to look around my heightmap that I have created. I've looked for tutorials and such on the web but I can only seem to find camera systems that involve moving the object, I dont want this, I want to draw the image and then look around it by moving the camera's position. Is this possible just by using gluookAt()? To start with I want to keep the camera looking at the centre of my heightmap the entire time, so I would have thought I only need a function for each of the first 3 parameters of the gluLookAt function (eyeX, eyeY, eyeZ) to move the camera round. Is this correct? And if so could you point me in the direction of a guide that would help me do this, I understand the level of maths I would need to use but it's linking this maths with the 3D coordinate system that gets me in a muddle! Sorry if its a stupid question but I'm a bit of a newbie to openGL and programming in general so I would appreciate any help. Thanks.

Share this post


Link to post
Share on other sites
Trienco    2555
What you are asking for is a little like a way to take a picture of a beach and then magically walking around inside the picture. You can't. It's a 2D snapshot of the scene. If you want to change what you see on the picture, you obviously have to take another one from a different angle (ie draw your stuff again). All you can do is move the picture around in front of your eyes (basically rendering to texture and move a textured rectangle around the screen), which most likely isn't what you want.

The reason people do cameras by "moving the objects" is because it's the same. Not just because if you move to the left, everything else seems to be moving to the right, but because the resulting matrix for moving the camera left is virtually the same as the matrix to move the world to the right. gluLookAt does nothing but setting up the modelview matrix with the inverse of the cameras matrix, effectively moving the world the opposite way.

Share this post


Link to post
Share on other sites
haegarr    7372
For a full description you have to dive into matrix math with transformations. But for the basic understanding it is sufficient to look at translational transformations only. Notice please that the following is the way of thinking that the camera should be part of the world.

Assume your camera is located at a position given by the point c. Here the co-ordinates of c are assumed to be given w.r.t. the "world", i.e. in the global co-ordinate system. Assume furthur you have a mesh located at the point m, also given w.r.t. the global co-ordinate system.

When it comes to rendering, you have to make the camera the "center of the world". This is because rendering happens in the viewing rectangle on your monitor, and the graphics hardware defines that rectangle to be located at zero. To get this, you subtract the camera's position from everything related to the world. This becomes clear when looking at the camera itself: Its new position will become
c' := c - c == 0
what is exactly what we want. Notice please that subtraction here is to be interpreted as "applying the inverse transformation"!

Similarly, the new position of the mesh becomes
m' := m - c
That is, looking at the structure of the formula, nothing else than a translational transformation of the mesh! And due to the subtraction the translation is along the opposite direction. That is what Trienco means: E.g. shifting the camera to the right has the same effect as shifting the world (the mesh in this case) to the left.

Extending this to matrices looks as follows. The local co-ordinate frame (from which the position is a part of) of the camera w.r.t. the global frame is
CG
and the same of the mesh is
MG

Applying the inverse transformation of CG to the mesh hence means
CG-1 * MG
(I'm using column vectors here, as OpenGL does).

The left part is called the "view matrix" (at least OpengGl does so), and the right part is called the "model matrix". In total it is the MODELVIEW matrix. It means in fact that 1st a mesh, given in its local co-ordinate frame, is 1st transformed into the global frame (done by the model matrix) and the result is then transformed into the camera's local frame (done by the view matrix).

Share this post


Link to post
Share on other sites
mpledge52    138
What about if I were to redraw the image every time the camera position was changed, would it be possible to just use the gluLookAt() function to view it from a different perspective, rather than changing the objects position?

I just seems more logical to me to have a couple of functions to control the position of the camera rather than translating the object.

Cheers.

Share this post


Link to post
Share on other sites
haegarr    7372
Manipulating the camera as it were an object in the world is usual. That is exactly why OpenGL deals with both the VIEW and the MODEL matrix (although it deals with them in a combined manner). gluLookAt can be used for that purpose.

However, perhaps here a misinterpretation of terms causes some confusion. When you say "draw an image" you perhaps mean instead "render the scene". You're, of course, able to re-render the scene each time the camera's position and/or orientation has changed, yielding in an adapted view into the scene (in a texture or on the screen). You're _not_ able to render the scene into an image (e.g. a texture) and navigate in a 3D manner inside the image. That is what Trienco has meant above.

Share this post


Link to post
Share on other sites
mpledge52    138
This is what i'm after: http://www.lighthouse3d.com/opengl/glut/index.php?6

There's the two functions orientMe and moveMeFlat which call gluLookAt after making adjustments to the camera position. I think all I need to do is add more similar functions so I can rotate around different axis and move in different directions but I dont understand how it works. I understand the x, y, and z values for the camera position but its the lx, ly, lz values defining the line of sight that I dont understand. Why do you need to change the line of sight when we are just moving backwards and forwards for example?

Is there anywhere that explains this in more depth?

Thanks again :)

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