Sign in to follow this  
afkboard

OpenGL How to define the vertices?

Recommended Posts

Hi, new to OpenGL and doing fine, just something I have to get answer to by professionals:

when you define a vertices for i.e. a square, and have something like:


float vertices[] = {
-1.0f, 1.0f, 0.0f, // 0, Top Left
-1.0f, -1.0f, 0.0f, // 1, Bottom Left
1.0f, -1.0f, 0.0f, // 2, Bottom Right
1.0f, 1.0f, 0.0f, // 3, Top Right
};





this defines vertices starting at x,y(-1.0, 1.0). I've seen some definitions of the vertices that start from i.e. x,y(1.25, 3.25) - which is basically the same as the sample above. How do you know where to define your vertices in the coordinating system since you can define them anywhere and then translate them wherever you want?

Another question: if I want to apply a texture on it, I also define something simillar to the above and having in mind that the texture has to be power of 2 (i.e. 256x256) - why create texture vertices that define oblong square? I kind of miss the point here, since through my application I define only one vertices for everything, but then seeing other examples and sources I understand that I am missing something, most of them use as many vertices definitions as needed for the elements to be drawn.

Thanks!

Share this post


Link to post
Share on other sites
The coordinates you pass can be placed anywhere. So what you do is place an identity matrix before you call the drawing function to "Zero" things out. So whatever you put in the world will always be centred at zero. All objects will start out like that, and then you translate and rotate it according to your tastes.

That's what I can understand from the first question. Otherwise you'd be talking about the projection matrix and playing around with the "camera".

The texture question is an easy one. When you define the vertices you can also pass arguments for the texture coordinates as well. This is a two dimensional coordinate that corresponds to the 2D coordinates on the image itself. I believe Googling glTexCoord will give you a better explanation.

You call glTexCoord first then the appropriate glVertex for which that texture point binds to.

If you're using OpenGL3.1 and up, then things change dramatically since glTexCoord and glVertex are obsolete, but that's another story for another day.

Share this post


Link to post
Share on other sites
Quote:
Original post by afkboard
this defines vertices starting at x,y(-1.0, 1.0). I've seen some definitions of the vertices that start from i.e. x,y(1.25, 3.25) - which is basically the same as the sample above.


How is it the same? The vertex positions are different.

Quote:
How do you know where to define your vertices in the coordinating system since you can define them anywhere and then translate them wherever you want?


If you translate your entire scene 100 units to the left and do the same to the camera, you will indeed get the same result (modulo floating point approximation).

So you simply have to make sure everything is defined correctly in relation to the camera.

Typically, each 3D object will be defined in a way that is ignorant of the rest of the scene. Your square, for example. If we wanted to "move" that square 100 units in the positive Y direction, or apply a rotation or scaling to it, then that would typically be done via the modelview matrix.

The OpenGL "red book" contains a good chapter on how the modelview matrix lets you position objects in relation to your camera. Older versions of the red book are available for free online. Grab a copy.

Quote:
the texture has to be power of 2 (i.e. 256x256)

This is only true in implementations of OpenGL that have a version number less than 2.x.

Quote:
- why create texture vertices that define oblong square?

Why not? Or, let me ask you a question: how would you draw a single textured triangle that isn't right-angled? How should OpenGL stretch and rotate the texture image to fit on that triangle?

The answer is that you have to tell it how. And since a square (or pretty much any other 3D object) in OpenGL is composed of triangles, you have to tell it about how to map parts of the texture on to all of those triangles.

I'm guessing your intuition is telling you that OpenGL should be able to figure out how to map a texture on to a square for you. I hope you see now that a square is a special case.

Again, read through the red book. It's quite friendly and will tell you about texture coordinates, texture transforms and so on.

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  

  • Forum Statistics

    • Total Topics
      627719
    • Total Posts
      2978789
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
  • Popular Now