Sign in to follow this  
DerUnterMensch

OpenGL 3D rendering of bilinear surface patch

Recommended Posts

This may be the incorrect thread, and the subject may not describe my issue very well, but I ask that you bear with me. I'm currently working on a renderer for bilinear surface patches just as a fun little side project and I've currently got my algorithm spitting out a list of ordered vertices as the patch is sampled. I'm having a problem figuring out how best to reorder the vertices in to a vertex array for rendering as a 3D mesh. I know it's basically the same process as polygonizing a height map, however instead of one value for each point, I've got three and I'm not exactly sure the best way to render the data. When thrown straight in to an array and rendered as points using GL_POINT in OpenGL I get the desired shape of the surface patch (This would mostly likely work in DirectX as well so it's not an API dependent question), however it's not really 3D and it's a very bad way to render a vertex array and nothing can really be done with the data as there aren't any polygons. I've been thinking that reordering all the vertices in order to create triangle strips would be expensive so perhaps an index array would work, however I'm not sure how best to calculate the indices. Any help would be appreciated as this has been bugging me for days and I can't seem to see the answer or come up with a clean algorithm for reordering the vertices into triangle strips. For clarification in case it's necessary:
current vertex array:
x1, y1, z3, x2, y2, z3, x4, y4, z4, etc..

Need to reorder or index so that triangle strip looks something like:

(x1,y1,z1)--------(x2,y2,z2)-----------(x3,y3,z3)
|                  /|                     /
|                /  |                  /
|              /    |               /
|            /      |             /
|           /       |           /
(x4,y4,z4)/         (x5,y5,z5)/

Share this post


Link to post
Share on other sites

Hi,

You should go with indexed triangle lists, using indexed triangle strips will just give you some extra head ache (need of degenerated triangles to join strips together).

You don't need to re-order any vertices, assuming that they are in a grid shape.

Here's a little example for the indexed tri-list:

The vertex layout:

0-1-2
|/|/|
3-4-5
|/|/|
6-7-8

The index buffer (put on different lines to show different triangles)

0,1,3,
1,3,4,
1,2,4,
2,4,5,
3,4,6,
4,7,6,
4,5,7,
5,8,7

I think that you should study the matter on the paper to find out the rule used here.

Good luck!

Share this post


Link to post
Share on other sites
RobTheBloke: Thanks for the source. I looked at it briefly and I'm not entirely sure it really helps as the vertices appear to already be assumed to be in the correct order unless I'm mistaken.

kauna:I have figured that an indexed array would probably be the best way to do what I'm after, however I'm not 100% sure how they work anymore as I tend to avoid them because they make normal calculations a bit less straightforward. From your example I would be doing something like this?:


vertexArray = {x1,y1,z1, x2,y2,z2, x3,y3,z3, x4,y4,z4}
indexArray = {0,0,0, 1,1,1, 2,2,2, 1,1,1, 3,3,3, 2,2,2}

Where the polygon looks like:

P0-P1
| / |
P2-P3

and is wound clockwise.



[Edited by - DerUnterMensch on January 30, 2008 1:57:58 PM]

Share this post


Link to post
Share on other sites
Quote:


I have figured that an indexed array would probably be the best way to do what I'm after, but I can't really remember how to do indexed arrays and can't seem to find any of my books on either DirectX or OpenGL.


DirectX SDK (for example) should have examples about using indexed primitives.

Quote:

When provided with an array of vertices the API looks for a single index for every three vertices in the vertex array? Or is it more complicated?


When using triangle list, the API reads 3 indices at a time from the index buffer and makes one triangle out of them (by using the vertices defined in the vertex buffer).

So, when defining triangle list the index buffer has three times as many indices as there is triangle primitives.

Quote:

Regrettably even if I can find my books and refresh on index arrays, I've no idea how to calculate the indexes algorithmically as I want to be able to control the resolution of the patch on runtime so I can't simply work out the indexes and expect them not to change.


I am not sure what you are talking about. Are you trying to implement some sort of LOD algorithm?

If I am not totally mistaken about your question, the following code would do the work for you.



//Something like this

for(int y = 0; y < NumVerticesY-1; ++y)
{
for(int x = 0; x < NumVerticesX-1; ++x)
{
int Index = y * NumVerticesX;

*indices++ = Index;
*indices++ = Index+1;
*indices++ = Index+NumVerticesX;

*indices++ = Index+1;
*indices++ = Index+NumVerticesX;
*indices++ = Index+NumVerticesX+1;
}
}




Regards!


Share this post


Link to post
Share on other sites
Quote:
Original post by DerUnterMensch
kauna:I have figured that an indexed array would probably be the best way to do what I'm after, however I'm not 100% sure how they work anymore as I tend to avoid them because they make normal calculations a bit less straightforward.


Having index array shouldn't really affect the way you calculate your normals.


Quote:


vertexArray = {x1,y1,z1, x2,y2,z2, x3,y3,z3, x4,y4,z4}
indexArray = {0,0,0, 1,1,1, 2,2,2, 1,1,1, 3,3,3, 2,2,2}

Where the polygon looks like:

P0-P1
| / |
P2-P3



Your index array should look like:

indexArray = {0,1,2,1,3,2}

and usually vertices have more components than just position (such as normal, texture coordinates etc).

Share this post


Link to post
Share on other sites
Quote:
...and usually vertices have more components than just position (such as normal, texture coordinates etc).


I tend to send vertices, normals, and texture coordinates to the GPU in separate arrays. When I know the mesh isn't going to be messed with I try to package everything together, but repacking an array constantly for a program that changes the normals or texture coordinates every frame and doesn't touch the rest is a pest.

Quote:
I am not sure what you are talking about. Are you trying to implement some sort of LOD algorithm?


At the moment I'm sampling the patch in increments to give me a 10x10 grid of points, but if I were to make it to were the program could sample more or less often the number of points would change. This would break most of the ways I can think of calculating the indices so that the grid would render as triangle strips as I can't simply say a polygon is vertexArray[x], vertexArray[x+1], and vertexArray[x+1*gridWidth] or something like that as the vertices are in groups of three and x would be the x coord, x+1 would be the y coord (not the x coord of the next point), and x+1*gridWidth would be something completely wrong.

Quote:
If I am not totally mistaken about your question, the following code would do the work for you.


Perhaps this is exactly what I'm trying to do but I don't think so. I guess I'm just going to have to leave this unsolved and go back to basics as I seem to have allowed myself to forget way to much after I wrote my engine to do all this stuff for me (though I never did finish a model loader so I don't have any code relevant to this sort of problem, though an imported mesh is usually ordered correctly from the start, so that probably wouldn't help anyways).

Share this post


Link to post
Share on other sites

Hi,

I think that you are trying to do things a bit in hard way.



Quote:

...but repacking an array constantly for a program that changes the normals or texture coordinates every frame and doesn't touch the rest is a pest.


It is quite the same to change normals or texture coordinates was the data in vertex structures or in separate arrays. So, constant repacking shouldn't be needed.

Quote:

At the moment I'm sampling the patch in increments to give me a 10x10 grid of points, but if I were to make it to were the program could sample more or less often the number of points would change.


It is perfectly ok to resample or recreate your patch vertices/indices if you want to present it in a different sampling resolution. In the case you are doing it very often so that it creates some significant overhead, then (and only then) you might consider a more complicated solutions.

However, I'd first work out the simple and working version, then do the profiling to see if it requires some optimisations.

As a programmer you'll need to define yourself the rules how your system works. For example, for triangulating a grid I have made a rule which works. Although it works only for grids, thats enough because it is only used with grids.

If you have just a bunch of vertices, there is absolutely no way to figure out the correct triangulation.

Cheers!

Share this post


Link to post
Share on other sites
Quote:
Original post by DerUnterMensch
RobTheBloke: Thanks for the source. I looked at it briefly and I'm not entirely sure it really helps as the vertices appear to already be assumed to be in the correct order unless I'm mistaken.


they are ordered as such


idx=0;
for(i=0;i<divsu;++i)
{
for(int j=0;j<divsv;++j)
{
verts[idx] = evalAt(i,j);
++idx;
}
}


The tri strips then get generated as...


0 1 2 divsv-1
| / | / | /
divsv+0 divsv+0 divsv+2 .... divsv+divsv-1


or something along those lines anyway.

Share this post


Link to post
Share on other sites
I think I've got it now. Thanks to you both. Most of my trouble was that I was letting it bother me too much because I couldn't figure it out. Now I just have to see how complicated I can make this thing. I wonder if it's possible to create a high res planet mesh by tiling bilinear patches, though I suppose the terrain would be unrealistically smooth.

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
      628293
    • Total Posts
      2981867
  • Similar Content

    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now