Sign in to follow this  
radioact1ve

OpenGL Points jumping...

Recommended Posts

radioact1ve    136
Hey everyone! I'm getting some weird results with very basic ogl code. It's all samples from "Beginning OpenGL GP" book. I'm just testing the water, VERY basic stuff. Basically: glBegin(GL_POINTS) glVertex3f(0.0, 0.0, 0.0); glVertex3f(1.0, 0.0, 0.0); glVertex3f(2.0, 0.0, 0.0); glEnd(); This does what I expect, three points: . . . But when I do this, change a 'y' value: glBegin(GL_POINTS) glVertex3f(0.0, 0.0, 0.0); glVertex3f(1.0, 3.0, 0.0); glVertex3f(2.0, 0.0, 0.0); glEnd(); results: (Ignore the '-' I couldn't get the spacing to work so I just put those in to show what the points are doing.) -. . . Something like that. For some reason, it jumps away from the previous 'x' spot (the middle). Shouldn't it be doing this: --. .--- . As I said, I'm totally new to ogl, so I'm going over the code from the book like crazy (just chapter 3 so I might be missing something), looking for some state/setting that could be causing this. Can anyone think of any? Or would it be better if I post the code? Thanks a lot everyone!! Greatly appreciate it. Just in case for those that have the book. I'm messing with the code from Chapter 3 pg. 46. [Edited by - radioact1ve on November 27, 2005 1:42:02 AM]

Share this post


Link to post
Share on other sites
Seroja    280
Just a guess, but how have you setup your modelview and prjection matrices?
(e.g. ortho or frustum/perspective? Any glRotate/glTranslate?)
Although quite unlikely, you could get such results after a couple of transformations.

Share this post


Link to post
Share on other sites
radioact1ve    136
Hey Seroja,

Thanks for the reply. In regard to those functions, this all I could find in the code. Of course I'm not really familiar with this, so I have no idea whats going on. 8)


glMatrixMode(GL_PROJECTION); // set projection matrix current matrix
glLoadIdentity(); // reset projection matrix

// calculate aspect ratio of window
gluPerspective(52.0f,(GLfloat)width/(GLfloat)height,1.0f,1000.0f);

glMatrixMode(GL_MODELVIEW); // set modelview matrix
glLoadIdentity();

Share this post


Link to post
Share on other sites
Seroja    280
So your code is:

glMatrixMode(GL_PROJECTION); // set projection matrix current matrix
glLoadIdentity(); // reset projection matrix

// calculate aspect ratio of window
gluPerspective(52.0f,(GLfloat)width/(GLfloat)height,1.0f,1000.0f);

glMatrixMode(GL_MODELVIEW); // set modelview matrix
glLoadIdentity();


glBegin(GL_POINTS)
glVertex3f(0.0, 0.0, 0.0);
glVertex3f(1.0, 0.0, 0.0);
glVertex3f(2.0, 0.0, 0.0);
glEnd();

// Or

glBegin(GL_POINTS)
glVertex3f(0.0, 0.0, 0.0);
glVertex3f(1.0, 3.0, 0.0);
glVertex3f(2.0, 0.0, 0.0);
glEnd();




It is strange that you see anything at all. Do you have any more setup code?
You draw the points at 0 Z. But your near plane is 1. You should not see anything. (Never tried points though, always used polygons)

How about trying to to make it a triangle?


glDisable(GL_LIGHTING); // No lighting
glDisable(GL_CULL_FACE); // No face culling
glBegin(GL_TRIANGLES)
glColor3f(1.0, 0.0, 0.0); // Red
glVertex3f(0.0, 0.0, 0.0);
glVertex3f(1.0, 3.0, 0.0);
glVertex3f(2.0, 0.0, 0.0);
glEnd();




I wonder whether you'll see your triangle at all.

If not, return to points, and add before the glBegin:
glTranslatef(0.0, 0.0, -5.0);

Share this post


Link to post
Share on other sites
radioact1ve    136
Oh no no... sorry! :) That's not how the code is.


Render() // My Render function
{
float pointSize = 0.5;
//float yPos = -15.0;

// clear screen and depth buffer
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
glLoadIdentity();
gluLookAt(0.0, 6.0, 0.1, 0.0, 0.0, 0.0, 0.0, 1.0, 0.0);

// draw a line of points of increasing size
for (float point = -4.0; point < 5.0; point+=0.5)
{
// set the point size
glPointSize(pointSize);

// draw the point
glBegin(GL_POINTS);
//glVertex3f(point, 5.0, 0.0);
glVertex3f(point, 0.0, 0.0);
glEnd();

// increase the point size for the next point
// yPos += 1.0;
pointSize += 1.0;
}
}



And then a SetupProjection()
SetupProjection(int width, int height)
{
if (height == 0) // don't want a divide by zero
{
height = 1;
}

// reset the viewport to new dimensions
glViewport(0, 0, width, height);

// set projection matrix current matrix
glMatrixMode(GL_PROJECTION);
glLoadIdentity(); // reset projection matrix

// calculate aspect ratio of window
gluPerspective(52.0f,(GLfloat)width/(GLfloat)height,1.0f,1000.0f);

glMatrixMode(GL_MODELVIEW); // set modelview matrix
glLoadIdentity(); // reset modelview matrix

m_windowWidth = width;
m_windowHeight = height;
}



As for that triangle, I got a really small/weird red right triangle. But I did see something

Share this post


Link to post
Share on other sites
Seroja    280
Quote:
Original post by radioact1ve
Oh no no... sorry! :) That's not how the code is.

*** Source Snippet Removed ***

And then a SetupProjection()
*** Source Snippet Removed ***

As for that triangle, I got a really small/weird red right triangle. But I did see something


Well now that you say you got gluLookAt it starts making sense.
I never used it so I can't tell you what to do, but experimenting a bit I think it is that call that is causing you the trouble. After transformations, seems like the Y axis that you are trying to change isn't Y axis anymore.

Try to remove that call, and instead translate back a bit to see what you're drawing.

Share this post


Link to post
Share on other sites
Seroja    280
You managed to get me confused about transformations for a whole 15 minutes :P
OK, so you are trying to render this:
-O-
O-O
Right?

Then don't do gluLookAt. Think of it as a drawing canvas. By calling gluLookAt you move the canvas. But instead of moving it away from you a bit just to see what is drawn, you also rotate it. Thus, Y axis as you think of it is now not really Y, but a different one. I don't want to get into gluLookAt to see exactly what transformations it does, but I'm 99% certain that you are drawing on a canvas that is not facing you (!) and thus get unusual results.

Use the following:


Render() // My Render function
{
float pointSize = 0.5;
//float yPos = -15.0;

// clear screen and depth buffer
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
glLoadIdentity();
//gluLookAt(0.0, 6.0, 0.1, 0.0, 0.0, 0.0, 0.0, 1.0, 0.0);
glTranslatef(0.0, 0.0, -6.0);

// draw a line of points of increasing size
for (float point = -4.0; point < 5.0; point+=0.5)
{
// set the point size
glPointSize(pointSize);

// draw the point
glBegin(GL_POINTS);
//glVertex3f(point, 5.0, 0.0);
glVertex3f(point, point/2, 0.0);
glEnd();

// increase the point size for the next point
// yPos += 1.0;
pointSize += 1.0;
}
}




This will draw the points in diagonal-up. You can later change the code to draw only one of the points a bit above.

Share this post


Link to post
Share on other sites
CRACK123    235
I would advise you to read up gluLookAt and understand it. However I think what you want is gluLookAt(0, 0, 6, 0, 0, 0, 0, 1, 0); This should give the same effect as glTranslatef(0, 0, -6).

Share this post


Link to post
Share on other sites
Seroja    280
Quote:
Original post by CRACK123
I would advise you to read up gluLookAt and understand it. However I think what you want is gluLookAt(0, 0, 6, 0, 0, 0, 0, 1, 0); This should give the same effect as glTranslatef(0, 0, -6).


Were you talking to me, saying to read about gluLookAt? If so, I don't need it. I prefer Rotate & Translate, that way I'm sure what I'm doing.

And if I understand correctly, gluLookAt(0, 0, 6, 0, 0, 0, 0, 1, 0) will actually move the camera forward 6 and reverse it. glTranslatef(0, 0, -6) moves the camera backward.
I could be wrong, but I think the correct one would be gluLookAt(0, 0, -6, 0, 0, 0, 0, 1, 0). (Why not use Translate?)

Share this post


Link to post
Share on other sites
CRACK123    235
Quote:
Original post by Seroja
Quote:
Original post by CRACK123
I would advise you to read up gluLookAt and understand it. However I think what you want is gluLookAt(0, 0, 6, 0, 0, 0, 0, 1, 0); This should give the same effect as glTranslatef(0, 0, -6).


Were you talking to me, saying to read about gluLookAt? If so, I don't need it. I prefer Rotate & Translate, that way I'm sure what I'm doing.

And if I understand correctly, gluLookAt(0, 0, 6, 0, 0, 0, 0, 1, 0) will actually move the camera forward 6 and reverse it. glTranslatef(0, 0, -6) moves the camera backward.
I could be wrong, but I think the correct one would be gluLookAt(0, 0, -6, 0, 0, 0, 0, 1, 0). (Why not use Translate?)



I was talking to the actual poster. And gluLookAt does it the opposite way of how you described it. Nothing wrong in using Translate. But eventually you will have a look at code to set up your camera wether you use gluLookAt or roll your own version of it. So its a good idea to understand it as well. Even better to see what it does under the hood but that can be done later.

To be technically correct glTranslate moves the axis and not a camera. For something as simple as this gluLookAt is not necessary but it has its usefulness.

Share this post


Link to post
Share on other sites
deavik    570
radioact1ve, your gluLookAt problem should be easy to explain:

Your original code was:
gluLookAt(
0.0, 6.0, 0.1,
0.0, 0.0, 0.0,
0.0, 1.0, 0.0);

The first three params are the (x, y, z) position of the camera. The next 3 are the (x, y, z) of the point you are looking at. Hence in your code the camera is roughly 6 units on the positive y-axis looking down at the origin (round-about where you are drawing your funky stuff). So far so good.

(The next 3 params denote the up-vector which is quite what it is named, by the way)

Now think about what is happenning--your camera is positioned on the y-axis, and your points are all on the x-y plane. You will perceive the difference between points at diferent x positions, but points on the same y-coordinates will look almost superimposed (at (0, 0, 0) they will be superimposed but not quite at other x-cordinates because the projection is non-orthographic).

So, the simple solution (as has been posted already) is to position your camera on the z-axis.
gluLookAt(
0.0, 0.0, 6.0,
0.0, 0.0, 0.0,
0.0, 1.0, 0.0);


And that's it! Read the related chapter of the red book [here] to get a clearer picture.

Share this post


Link to post
Share on other sites
radioact1ve    136
Quote:
Original post by Seroja
You managed to get me confused about transformations for a whole 15 minutes :P


lol my bad!!

Your code worked great! That's exactly what I wanted to do. Not sure what I did or how, but I can take care of that by doing a little more reading. Definitely look into all the suggestions put in, especially LookAt and Translate.

Thxs everyone for your help!! Totally kick ass! Got to start reading.



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