Sign in to follow this  
jaronimo

OpenGL VBO generation at runtime

Recommended Posts

Hi everyone!

I'm currently trying to implement a random terrain generator using OpenGL.. and since I wanna go with the times I'm planning to do the whole thing in OpenGL 3.0 and therefore use VBOs.
since the user will be able to adjust the terrain size at runtime, the point grid VBO will not have a fixed size.. so I'm trying to come up with an algorithm that calculates a vertex grid of resolution n*n (n is user specified) and also calculates all the indices which I guess is the tricky part..

what I wanted to ask: is there an established way in which this sort of thing should/could be done? I'm currently trying to figure something out.. but I don't want to reinvent the wheel, so if anyone has any suggestions, please let me know!

thanks,
jaronimo

Share this post


Link to post
Share on other sites
You could've raycast the terrain in screen space with just a shader and a heightmap.
You can modify the texture fast, and it can give a real neat-looking result while circumventing the need for vertices almost completely.

Share this post


Link to post
Share on other sites
sounds intriguing! but after googling around for quite a while now, I think I'll try the VBO approach since I'm not really familiar with raycasting.. or do you know a good tutorial?

for example, with raycasting, would it be possible to rotate the heightmap? or could I just look at it from my camera position?

Share this post


Link to post
Share on other sites
Quote:
Original post by jaronimo
sounds intriguing! but after googling around for quite a while now, I think I'll try the VBO approach since I'm not really familiar with raycasting.. or do you know a good tutorial?

for example, with raycasting, would it be possible to rotate the heightmap? or could I just look at it from my camera position?


Yes it will be possible to rotate as much as you like. This old technique should work for 4DOF at first, as it uses a simple column approach.
That's the advantage with heightmaps here, when each column of pixels cast
we can guarantee that (if we go from the bottom to the top of screen) the point where we hit the landscape is further away every time, and we can approximate the hit spot every time after the first ray.

It's really simple, and this tutorial, though a little old, explains the technique just fine. You can do what it does in a fragment shader;

Voxel terrain on flipcode

This is also good:

Voxel terrain on codermind

But more modern techniques are ready for 6DOF translations, but I can't find any tutorials on that for you. You should give the above articles a go.

Share this post


Link to post
Share on other sites
so, I continued with the VBO approach anyway, since I can use parts of my code for another course this way.

...and I hit a roadblock that I can't seem to get past.. I'm quite sure it's a noob problem too, but I really can't figure it out...

my program has no problem rendering this points array for my VBO:

GLfloat points[] = { 0.0f, 0.0f, 0.0f, 1.0f,
1.0f, 0.0f, 0.0f, 1.0f,
2.0f, 0.0f, 0.0f, 1.0f,
0.0f, 1.0f, 0.0f, 1.0f,
1.0f, 1.0f, 0.0f, 1.0f,
2.0f, 1.0f, 0.0f, 1.0f,
0.0f, 2.0f, 0.0f, 1.0f,
1.0f, 2.0f, 0.0f, 1.0f,
2.0f, 2.0f, 0.0f, 1.0f};

but when I try this instead, nothing is rendered:

GLfloat* points = generateVBO(dimension);

generateVBO() looks like this:

GLfloat* generateVBO(int dim){

GLfloat genPoints[] = { 0.0f, 0.0f, 0.0f, 1.0f,
1.0f, 0.0f, 0.0f, 1.0f,
2.0f, 0.0f, 0.0f, 1.0f,
0.0f, 1.0f, 0.0f, 1.0f,
1.0f, 1.0f, 0.0f, 1.0f,
2.0f, 1.0f, 0.0f, 1.0f,
0.0f, 2.0f, 0.0f, 1.0f,
1.0f, 2.0f, 0.0f, 1.0f,
2.0f, 2.0f, 0.0f, 1.0f};

return genPoints;
}

of course this is not the original code but I dumbed it down to this to find out why it is not rendering.. I thought, this HAS to work since the array is not generated dynamically. I just return the same array as a pointer.. but this shouldn't be a problem, should it?

i mean glBufferData() even needs a pointer to the data, so why is nothing rendering when I give it a pointer instead of an actual array?
glBufferData(GL_ARRAY_BUFFER, 24*4*sizeof(GLfloat), (GLfloat*)points, GL_STATIC_DRAW);

Share this post


Link to post
Share on other sites
You need to allocate genPoints on the heap (hint, use 'new'), not on the stack. When generateVBO exits, the array genPoints is destroyed, leaving your GLfloat* pointer pointing to destroyed data.

Share this post


Link to post
Share on other sites
thanks for the tip.. I now found out what the real problem was ;(
quite embarrassing really.. it did not work because the real code had an infinite loop because I wrote i=+4 in the for loop... yikes

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
      627735
    • Total Posts
      2978854
  • 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