• Advertisement
Sign in to follow this  

OpenGL Looking for heightmap (not landscape) optimization

This topic is 4486 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi everybody, I feel a bit lost with my latest OpenGL project. I'm looking for a solution to optimize my rendering that displays a surface that is rendered from a 1000 x 1000 height map (yes, that's 1 million vertices, all visible at once, currently). The surface which is rendered from the height map is usually completely visible to the user, therefor I don't have any culling algorithms involved. The surface is just plain flat shaded in several colors, so no texturing is done - however it's getting slow lately. I was able to save a lot of vertex transfers by using triangle or quad strips, which made it render about 50% faster. I also tried display lists, but they always make it crash if used with too much vertices. I didn't try vertex arrays yet; probably that'd give it another boost on performance. The best idea would be to reduce the number of shown polys, but I'm not sure which is the best approach. I could either try to reduce the tri/quad count by trying to merge tris/quads that are next to each other and have the same face normal (like a lossless mesh simplification) - or I could try to dynamically reduce the tri/quad count for spots that are far away (LOD). I read a lot about mesh simplification, tesselation, and LOD algos during the last days, but now I feel even more lost. Most stuff I read was about terrain rendering (where you usually only see a small area of the heightmap) and mesh simplification that was intended to be done before rendering (not in realtime). I'd appreciate any hints and ideas on how I could speed up my rendering

Share this post


Link to post
Share on other sites
Advertisement
Hi,

The easiest way for you to get some more speed would be to use vertex buffer objects (if you have it implemented with vertex arrays then you are pretty much there).
However, I can't think of many reasons for rendering such a big mesh unless you are making some sort of level editing/creation application. In which case, surely you don't need to update it that often.

Heightmap lod algorithms have their advantages and disadvantages depending on the situation, so if you do want to implement lod you should have a look at roam, clod and geomipmapping (among others [smile]) and see which one would best suit your needs.

Regards,
ViLiO

Share this post


Link to post
Share on other sites
Yes I definitely should give vertex buffer objects a try. I'm still in the progress of learning how they work :)

But I'm confused about what is written about optimizations. At several places I read that ROAM is not very useful anymore today. With nowadays cards, it's told to be more effective to let the GPU handle the additional vertices than keeping the CPU busy with ROAM calculations. I wonder if this would still apply to my case (1 million vertices sounds very high to render them all to me, and maybe I need to go even higher)

I wonder if I should concentrate on reducing the tri/quad count somehow (ROAM) or on increasing processing speed (e.g. by using vertex buffer objects).

Share this post


Link to post
Share on other sites
Hi again,

I must admit I am puzzled by your need to render so much data all at the same time [smile]. You say the whole heightmap is visible most of the time ...but in which way do you view it? If you are looking across the mesh from a low camera angle then you were benefit greatly from some sort of lod (probably geomipmapping) and of course you could make use of occlusion. Lod would allow you to greatly reduce the vertex count of the parts of the heightmap that are far from the camera. Occlusion has obvious benefits [grin]
It would be a good idea to split your heightmap up into 65x65 chunks anyway, as having a vertex buffer object that is too large causes slowdown (65x65 vertices is good for most hardware but you can of course experiment). The whole heightmap can also be tri-stripped quite easily.

Best of luck,
ViLiO

Share this post


Link to post
Share on other sites
It's hard to explain what the project does that I'm working on. The user can see an object from above and modify its surface at runtime. It looks a little like you would write letters with your finger into the sand. The user usually looks at the working object from above, but he should be able to zoom in a lot without loosing too much details. So I created a huge height map which has a high enough resolution and used it to present my objects surface. Unfortunately my first attempt to draw a quad onto each 4 adjacent heights to form a surface worked first, but (of course) became extremely slow now that the heightmap became so huge.

I don't necessarily need to render all the data of the heightmap. If the user has zoomed out, there's no need to render every vertex, because they can't be distinguished anyway :). It's just that I need to store the data in such a high resolution so that the user would be able to zoom in and see details.

LOD, ROAM, Geomipmapping, I read a lot about all the methods and I think I basically understand them all, but where I'm getting more and more confused is that all articles and papers I read are related to terrain rendering (which is somewhat different to what I do, e.g. in my case the heights aren't fixed and geomipmaps can't be precalculated, and the user usually sees the whole heightmap area, not only a small part of it (which would make frustum culling useless, at least unless the user doesn't zoom in a lot)

I was also thinking about partitioning the heightmap into several smaller pieces by using a quadtree and somehow using some of the tree nodes to generate geomipmaps in realtime, but I'm not sure if that wouldn't drastically increase the memory usage (e.g.for linking so many tree nodes)

In some articles they mentioned that nowadays it's often faster/better to let the GPU handle some additional polygons than wasting CPU cycles for removing invisible polygons. E.g. in my case a user would watch the whole object 90% of his time, which makes frustum culling useless. Even if he zooms in, I'd say that at a maximum he still sees 50% of the object. That doesn't sound like frustum culling would make sense in my case - but I'm just missing experience when it comes to this, and so I'm getting confused more and more :-)

Share this post


Link to post
Share on other sites
Well, the last thing I can suggest is parallax mapping.
I suspect I am about to go way over my head here considering I have never implemented parallax [grin].

From my limited knowledge, parallax is similar to bump mapping, only it gives the appearance of full displacement mapping (aka heightmap). This would mean you would only need to change texture data and not move individual vertices, so you could have a single quad with a 1024x1024 parallax map. The downside is that it is an image based technique and doesn't actually modify vertices, so if viewed from acute angles, you can see that the quad would actuall be flat.

Hopefully though i've given you some food for thought [smile]

All the best,
ViLiO

Share this post


Link to post
Share on other sites
Well I'm sure vertex buffer objects would help. They might not work for the same reason as display lists though. Try chopping your mesh into 4 or more chunks, and see if it can handle it then.

Not sure how much this will help, but it's something to try. When the user can see the whole thing, you obviously don't need that much detail (you probably have a near 1 to 1 ratio of poly's and pixels). Now your not the usual fps player that needs detail close up and not further away, your a high up observer. So, I suggest just dropping 3 quarters of the polys. Rather than making a mesh that uses every vertex, skip every second one. So,

.---.---.
| | |
.---.---.
| | |
.---.---.
becomes
.---.---.
| |
. . .
| |
.---.---.


You'll need the detail when you zoom in though, but hopefully then you can cull some of your mesh. Rather than doing it yourself, I'd recommend the vertex culling extension.

Share this post


Link to post
Share on other sites
I'm doing something similar and I'm doing this:

1) I create a mesh which is really simple and optimized then I save it into RAM
2) Move this mesh (usually 1024x1024) to the video card using VBO.
3) Load a heightmap and the corresponding normal map.
4) Displace the mesh in the vertex shader using texture fetch.
5) Do per-pixel lights with the pre-calculated normal maps
6) Done.

I normally get around 30-40 fps in a 6800gt. I'm sure you can get a better fps if you:
a) Divide the mesh into smaller chunks for optimization.
b) Cull the unnecessary polygons when zomming.

Hope that help.
:)

Share this post


Link to post
Share on other sites
From your description, it seems like the heightmap is mostly fixed. The exception is that every frame a relatively small area is changed. Assuming that is true, then a LOD terrain algorithm (particularly geomipmapping) is appropriate.

You wrote, "in my case the heights aren't fixed and geomipmaps can't be precalculated". That is not true.

The reason I suggest geomipmapping is how it implements LOD. In geomipmapping, LOD is achieved through a predetermined method of vertex selection and is independent of the data (except for determining the LOD thresholds). So when the heightmap changes, all you have to do is determine the new LOD thresholds. You could even skip that if you don't mind some popping.

Normally for rendering a terrain, I recommend "Chunked LOD", but it requires some preprocessing so it is probably not appropriate in this case.

Share this post


Link to post
Share on other sites
Thanks everybody. I'm still not sure how I should go on, but this gave me a good overview on which topics I should do deeper searches. From what I know now, I should mostly look into geomipmapping to decrease details of not-so-important (far away) places and maybe ROAM to reduce the overall number of tris.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By reenigne
      For those that don't know me. I am the individual who's two videos are listed here under setup for https://wiki.libsdl.org/Tutorials
      I also run grhmedia.com where I host the projects and code for the tutorials I have online.
      Recently, I received a notice from youtube they will be implementing their new policy in protecting video content as of which I won't be monetized till I meat there required number of viewers and views each month.

      Frankly, I'm pretty sick of youtube. I put up a video and someone else learns from it and puts up another video and because of the way youtube does their placement they end up with more views.
      Even guys that clearly post false information such as one individual who said GLEW 2.0 was broken because he didn't know how to compile it. He in short didn't know how to modify the script he used because he didn't understand make files and how the requirements of the compiler and library changes needed some different flags.

      At the end of the month when they implement this I will take down the content and host on my own server purely and it will be a paid system and or patreon. 

      I get my videos may be a bit dry, I generally figure people are there to learn how to do something and I rather not waste their time. 
      I used to also help people for free even those coming from the other videos. That won't be the case any more. I used to just take anyone emails and work with them my email is posted on the site.

      I don't expect to get the required number of subscribers in that time or increased views. Even if I did well it wouldn't take care of each reoccurring month.
      I figure this is simpler and I don't plan on putting some sort of exorbitant fee for a monthly subscription or the like.
      I was thinking on the lines of a few dollars 1,2, and 3 and the larger subscription gets you assistance with the content in the tutorials if needed that month.
      Maybe another fee if it is related but not directly in the content. 
      The fees would serve to cut down on the number of people who ask for help and maybe encourage some of the people to actually pay attention to what is said rather than do their own thing. That actually turns out to be 90% of the issues. I spent 6 hours helping one individual last week I must have asked him 20 times did you do exactly like I said in the video even pointed directly to the section. When he finally sent me a copy of the what he entered I knew then and there he had not. I circled it and I pointed out that wasn't what I said to do in the video. I didn't tell him what was wrong and how I knew that way he would go back and actually follow what it said to do. He then reported it worked. Yea, no kidding following directions works. But hey isn't alone and well its part of the learning process.

      So the point of this isn't to be a gripe session. I'm just looking for a bit of feed back. Do you think the fees are unreasonable?
      Should I keep the youtube channel and do just the fees with patreon or do you think locking the content to my site and require a subscription is an idea.

      I'm just looking at the fact it is unrealistic to think youtube/google will actually get stuff right or that youtube viewers will actually bother to start looking for more accurate videos. 
    • By Balma Alparisi
      i got error 1282 in my code.
      sf::ContextSettings settings; settings.majorVersion = 4; settings.minorVersion = 5; settings.attributeFlags = settings.Core; sf::Window window; window.create(sf::VideoMode(1600, 900), "Texture Unit Rectangle", sf::Style::Close, settings); window.setActive(true); window.setVerticalSyncEnabled(true); glewInit(); GLuint shaderProgram = createShaderProgram("FX/Rectangle.vss", "FX/Rectangle.fss"); float vertex[] = { -0.5f,0.5f,0.0f, 0.0f,0.0f, -0.5f,-0.5f,0.0f, 0.0f,1.0f, 0.5f,0.5f,0.0f, 1.0f,0.0f, 0.5,-0.5f,0.0f, 1.0f,1.0f, }; GLuint indices[] = { 0,1,2, 1,2,3, }; GLuint vao; glGenVertexArrays(1, &vao); glBindVertexArray(vao); GLuint vbo; glGenBuffers(1, &vbo); glBindBuffer(GL_ARRAY_BUFFER, vbo); glBufferData(GL_ARRAY_BUFFER, sizeof(vertex), vertex, GL_STATIC_DRAW); GLuint ebo; glGenBuffers(1, &ebo); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ebo); glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(indices), indices,GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, false, sizeof(float) * 5, (void*)0); glEnableVertexAttribArray(0); glVertexAttribPointer(1, 2, GL_FLOAT, false, sizeof(float) * 5, (void*)(sizeof(float) * 3)); glEnableVertexAttribArray(1); GLuint texture[2]; glGenTextures(2, texture); glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageOne = new sf::Image; bool isImageOneLoaded = imageOne->loadFromFile("Texture/container.jpg"); if (isImageOneLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageOne->getSize().x, imageOne->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageOne->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageOne; glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageTwo = new sf::Image; bool isImageTwoLoaded = imageTwo->loadFromFile("Texture/awesomeface.png"); if (isImageTwoLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageTwo->getSize().x, imageTwo->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageTwo->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageTwo; glUniform1i(glGetUniformLocation(shaderProgram, "inTextureOne"), 0); glUniform1i(glGetUniformLocation(shaderProgram, "inTextureTwo"), 1); GLenum error = glGetError(); std::cout << error << std::endl; sf::Event event; bool isRunning = true; while (isRunning) { while (window.pollEvent(event)) { if (event.type == event.Closed) { isRunning = false; } } glClear(GL_COLOR_BUFFER_BIT); if (isImageOneLoaded && isImageTwoLoaded) { glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glUseProgram(shaderProgram); } glBindVertexArray(vao); glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, nullptr); glBindVertexArray(0); window.display(); } glDeleteVertexArrays(1, &vao); glDeleteBuffers(1, &vbo); glDeleteBuffers(1, &ebo); glDeleteProgram(shaderProgram); glDeleteTextures(2,texture); return 0; } and this is the vertex shader
      #version 450 core layout(location=0) in vec3 inPos; layout(location=1) in vec2 inTexCoord; out vec2 TexCoord; void main() { gl_Position=vec4(inPos,1.0); TexCoord=inTexCoord; } and the fragment shader
      #version 450 core in vec2 TexCoord; uniform sampler2D inTextureOne; uniform sampler2D inTextureTwo; out vec4 FragmentColor; void main() { FragmentColor=mix(texture(inTextureOne,TexCoord),texture(inTextureTwo,TexCoord),0.2); } I was expecting awesomeface.png on top of container.jpg

    • By khawk
      We've just released all of the source code for the NeHe OpenGL lessons on our Github page at https://github.com/gamedev-net/nehe-opengl. code - 43 total platforms, configurations, and languages are included.
      Now operated by GameDev.net, NeHe is located at http://nehe.gamedev.net where it has been a valuable resource for developers wanting to learn OpenGL and graphics programming.

      View full story
    • By TheChubu
      The Khronos™ Group, an open consortium of leading hardware and software companies, announces from the SIGGRAPH 2017 Conference the immediate public availability of the OpenGL® 4.6 specification. OpenGL 4.6 integrates the functionality of numerous ARB and EXT extensions created by Khronos members AMD, Intel, and NVIDIA into core, including the capability to ingest SPIR-V™ shaders.
      SPIR-V is a Khronos-defined standard intermediate language for parallel compute and graphics, which enables content creators to simplify their shader authoring and management pipelines while providing significant source shading language flexibility. OpenGL 4.6 adds support for ingesting SPIR-V shaders to the core specification, guaranteeing that SPIR-V shaders will be widely supported by OpenGL implementations.
      OpenGL 4.6 adds the functionality of these ARB extensions to OpenGL’s core specification:
      GL_ARB_gl_spirv and GL_ARB_spirv_extensions to standardize SPIR-V support for OpenGL GL_ARB_indirect_parameters and GL_ARB_shader_draw_parameters for reducing the CPU overhead associated with rendering batches of geometry GL_ARB_pipeline_statistics_query and GL_ARB_transform_feedback_overflow_querystandardize OpenGL support for features available in Direct3D GL_ARB_texture_filter_anisotropic (based on GL_EXT_texture_filter_anisotropic) brings previously IP encumbered functionality into OpenGL to improve the visual quality of textured scenes GL_ARB_polygon_offset_clamp (based on GL_EXT_polygon_offset_clamp) suppresses a common visual artifact known as a “light leak” associated with rendering shadows GL_ARB_shader_atomic_counter_ops and GL_ARB_shader_group_vote add shader intrinsics supported by all desktop vendors to improve functionality and performance GL_KHR_no_error reduces driver overhead by allowing the application to indicate that it expects error-free operation so errors need not be generated In addition to the above features being added to OpenGL 4.6, the following are being released as extensions:
      GL_KHR_parallel_shader_compile allows applications to launch multiple shader compile threads to improve shader compile throughput WGL_ARB_create_context_no_error and GXL_ARB_create_context_no_error allow no error contexts to be created with WGL or GLX that support the GL_KHR_no_error extension “I’m proud to announce OpenGL 4.6 as the most feature-rich version of OpenGL yet. We've brought together the most popular, widely-supported extensions into a new core specification to give OpenGL developers and end users an improved baseline feature set. This includes resolving previous intellectual property roadblocks to bringing anisotropic texture filtering and polygon offset clamping into the core specification to enable widespread implementation and usage,” said Piers Daniell, chair of the OpenGL Working Group at Khronos. “The OpenGL working group will continue to respond to market needs and work with GPU vendors to ensure OpenGL remains a viable and evolving graphics API for all its customers and users across many vital industries.“
      The OpenGL 4.6 specification can be found at https://khronos.org/registry/OpenGL/index_gl.php. The GLSL to SPIR-V compiler glslang has been updated with GLSL 4.60 support, and can be found at https://github.com/KhronosGroup/glslang.
      Sophisticated graphics applications will also benefit from a set of newly released extensions for both OpenGL and OpenGL ES to enable interoperability with Vulkan and Direct3D. These extensions are named:
      GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_memory_object_win32 GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_semaphore_win32 GL_EXT_win32_keyed_mutex They can be found at: https://khronos.org/registry/OpenGL/index_gl.php
      Industry Support for OpenGL 4.6
      “With OpenGL 4.6 our customers have an improved set of core features available on our full range of OpenGL 4.x capable GPUs. These features provide improved rendering quality, performance and functionality. As the graphics industry’s most popular API, we fully support OpenGL and will continue to work closely with the Khronos Group on the development of new OpenGL specifications and extensions for our customers. NVIDIA has released beta OpenGL 4.6 drivers today at https://developer.nvidia.com/opengl-driver so developers can use these new features right away,” said Bob Pette, vice president, Professional Graphics at NVIDIA.
      "OpenGL 4.6 will be the first OpenGL release where conformant open source implementations based on the Mesa project will be deliverable in a reasonable timeframe after release. The open sourcing of the OpenGL conformance test suite and ongoing work between Khronos and X.org will also allow for non-vendor led open source implementations to achieve conformance in the near future," said David Airlie, senior principal engineer at Red Hat, and developer on Mesa/X.org projects.

      View full story
    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
  • Advertisement