• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
jmfurlott

OpenGL
Creating new triangles using GL_TRIANGLE_STRIPS

8 posts in this topic

Hello all,


Trying to render a model using GL_TRIANGLE_STRIPS and its working fine, however, at certain arbitrary points I want to break off the the triangle strips and essentially start a new set of triangle strips (that are completely separate from the original strips). How should I go about doing this? Multiple VBOs? I currently have only one VBO that holds all my vertices.

 

(OpenGL ES2.0 in particular but surely applies to OpenGL as a whole)

 


Thanks!

0

Share this post


Link to post
Share on other sites

You can do it with multiple draw calls just starting each at a different offset into your index buffer, no need to use multiple VBOs at all, but it's usually much more efficient to use degenerate triangles to 'stitch' strips together. For illustrative purposes (your strips are probably longer) imagine two quads and the following triangle strip indices to render them: 0, 1, 2, 3, 3, 4, 4, 5, 6, 7.

 

That's 10 indices, so 8 triangles. But triangle 2, 3, 3, triangle 3, 3, 4, triangle 3, 4, 4 and triangle 4, 4, 5 are degenerate, that is they have zero area, so they do not contribute to the scene at all. So only 4 triangles get rendered, just the two quads we wanted.

0

Share this post


Link to post
Share on other sites

You may want to also test if triangle strips are really best for you in the first place.

In my experience, starting with triangle lists and then adding triangle stripping later the performance actually decreased.  At my office we got the same results (our triangle-strippers are not related and use different algorithms).

Neither of us did a thorough investigation into why our triangle strips were slower than triangle lists, but the candidates are obvious: poor caching and extra triangles.

 

Degenerate triangles get culled early, but not early enough.  You take a hit for them.

And while there is less bandwidth due to smaller index buffers, it is not enough to make up for the better cache performance offered by triangle lists.

 

As a general rule of thumb, you should only use triangle strips when the index buffer’s size is below 60% of its triangle-list form.  When the index buffer is able to decrease by this much it means fewer degenerate triangles were generated and bandwidth is so significantly reduced that it can make up for the poorer cache.

 

Also, your mobile device uses a unified memory model, which means bandwidth is irrelevant, which means that by using triangle strips you only increase the triangle count and decrease the cache performance.  The only way in which triangle strips help you is in decreasing bandwidth, but on mobile devices there is no bandwidth issue in the first place, which means triangle strips are really just a way of shooting yourself in the foot.  You get all of the bad and none of the good.

 

Never blindly go with what is rumored to be the better way.  Always do your own testing.  You will likely find that you will have better performance with triangle lists than with triangle strips.

 

 

L. Spiro

Edited by L. Spiro
1

Share this post


Link to post
Share on other sites

Depending on the hardware being targetted, strips may yet be the best choice; mobile hardware (this is GL ES after all) is particularly known for flying in the face of what works better elsewhere.  If you do want to retain strip order, then using indexing will let you do that and will nicely cover the case where you need to join two strips; this will be cheaper than adding extra verts to make degenerates as indices are smaller than vertices.  Indexing can also cover cases where you need to add free triangles into your mesh, or even add in some fans, and all without any messing and with just one draw call per mesh.

 

Primitive restart can also do that, but since you're on ES2 you don't have primitive restart available, so do at least try a benchmark with just indexed triangles as in general terms (and as L Spiro says) they are the general-case fastest path nowadays; if you run into performance problems with those (or if you are on a class of mobile hardware where you know for absolute certain that strips are preferred) then is the time to start considering strips, not before.

 

Essential reading here: http://hacksoflife.blogspot.ie/2010/01/to-strip-or-not-to-strip.html

1

Share this post


Link to post
Share on other sites

You may want to also test if triangle strips are really best for you in the first place.

 

 

Also, your mobile device uses a unified memory model, which means bandwidth is irrelevant, which means that by using triangle strips you only increase the triangle count and decrease the cache performance.  The only way in which triangle strips help you is in decreasing bandwidth, but on mobile devices there is no bandwidth issue in the first place, which means triangle strips are really just a way of shooting yourself in the foot.  You get all of the bad and none of the good.

 

Whoa that is incredible. Thank you so much. I will first construct it using triangles.  I was just getting such terrible performance using strips and this could be way.  I will reconstruct my data using just standard GL_TRIANGLES.  

 

Do you have any more information about this bandwidth issue?

 

Thank you!

 

-jmfurlott

0

Share this post


Link to post
Share on other sites

Depending on the hardware being targetted, strips may yet be the best choice; mobile hardware (this is GL ES after all) is particularly known for flying in the face of what works better elsewhere.  If you do want to retain strip order, then using indexing will let you do that and will nicely cover the case where you need to join two strips; this will be cheaper than adding extra verts to make degenerates as indices are smaller than vertices.  Indexing can also cover cases where you need to add free triangles into your mesh, or even add in some fans, and all without any messing and with just one draw call per mesh.

 

Primitive restart can also do that, but since you're on ES2 you don't have primitive restart available, so do at least try a benchmark with just indexed triangles as in general terms (and as L Spiro says) they are the general-case fastest path nowadays; if you run into performance problems with those (or if you are on a class of mobile hardware where you know for absolute certain that strips are preferred) then is the time to start considering strips, not before.

 

Essential reading here: http://hacksoflife.blogspot.ie/2010/01/to-strip-or-not-to-strip.html

 

 

Depending on the hardware being targetted, strips may yet be the best choice; mobile hardware (this is GL ES after all) is particularly known for flying in the face of what works better elsewhere.  If you do want to retain strip order, then using indexing will let you do that and will nicely cover the case where you need to join two strips; this will be cheaper than adding extra verts to make degenerates as indices are smaller than vertices.  Indexing can also cover cases where you need to add free triangles into your mesh, or even add in some fans, and all without any messing and with just one draw call per mesh.

 

Primitive restart can also do that, but since you're on ES2 you don't have primitive restart available, so do at least try a benchmark with just indexed triangles as in general terms (and as L Spiro says) they are the general-case fastest path nowadays; if you run into performance problems with those (or if you are on a class of mobile hardware where you know for absolute certain that strips are preferred) then is the time to start considering strips, not before.

 

Essential reading here: http://hacksoflife.blogspot.ie/2010/01/to-strip-or-not-to-strip.html

 

Ah my question was already answered (didn't see this before replying).  Thank you guys...seems like normal triangles are the way to go for now.  I don't indices are good for my model because (based on input) they are continually changing.

0

Share this post


Link to post
Share on other sites

Do you have any more information about this bandwidth issue?

Nothing I could cite but you can read about unified memory models (UMM) in general online.
What it means for mobile devices is that the GPU and CPU share the same memory, unlike in desktops where they each have their own memory.
When a GPU has its own memory it can only access that memory, so whatever you want to draw has to, at some point, be transferred across the bus to the GPU RAM from the CPU RAM. How much and how fast you can transfer is “bandwidth”.

So for desktops your index and vertex buffers have to be copied, thus smaller is better.

For UMM, no copy has to take place since the GPU can access the vertex/index buffers directly wherever they are in “normal” RAM.
Smaller is still better, but not as significantly.
And there are still things that can cause a copy to take place by the driver (though it is just “normal” RAM to “normal” RAM, literally via memcpy()).
If you are not using a VBO, the entire vertex buffer will be copied.
If you are not using an IBO, the entire index buffer will be copied.
If your vertex-buffer elements are poorly aligned (for example using 6-bytes for positions) the entire vertex buffer will be copied, and slowly since it also realigns the vertex data.


L. Spiro Edited by L. Spiro
0

Share this post


Link to post
Share on other sites

Hello all,


Trying to render a model using GL_TRIANGLE_STRIPS and its working fine, however, at certain arbitrary points I want to break off the the triangle strips and essentially start a new set of triangle strips (that are completely separate from the original strips). How should I go about doing this? Multiple VBOs? I currently have only one VBO that holds all my vertices.

 

(OpenGL ES2.0 in particular but surely applies to OpenGL as a whole)

 


Thanks!

Under some circumstances, you can do the trick where you alpha out at the end of one strip and alpha back in at the start of the next.

(Still in the same draw call, -it's the same GL_TRIANGLE_STRIP, basically.)


I realize this seems very dirty, but I made it work, -it's easy and performs well when used with caution.

 

Make sure the triangles fading to transparent and the one connecting strips have zero area too, -and preferably hide them by applying high (enough) depth values, there's no need to process more fragments than necessary.

 

I used it for patches in a typical heightmap terrain, and there are probably many places where it won't perform well.

Edited by SuperVGA
0

Share this post


Link to post
Share on other sites

I don't indices are good for my model because (based on input) they are continually changing.

I didn’t see this before but now that I have I also recall you saying your performance was lower than you expected.

If you don’t update your VBO’s properly it will have a very huge impact on your performance (literally halving it).
Be sure you are updating your VBO’s properly either by using ring buffers or by orphaning your buffers before changing them.


L. Spiro
0

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  
Followers 0

  • Similar Content

    • By Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      https://github.com/sp4cerat/Planet-LOD
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      https://github.com/sp4cerat/Planet-LOD/blob/master/src.simple/Main.cpp
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
      Toastmastern
       
       
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
       
    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
  • Popular Now