Question

I’m rendering 2D polygons with the GLUTesselator the first time, then they are stored in a display list for subsequent use. I think VBO’s might be faster, but since I can’t access the stuff that the tesselator outputs, and since it uses mixes of gl_triangle, quad, strip etc, i’m not sure how I could do this, even though I would like to use VBO’s once the GLUTesselator is done with them for optimal performance. Thanks

Answer 1

It’s been a while since I’ve used the GLU tesselator, but as I recall it just adds standard triangles to your vertex list. One of the callback functions that you pass into it will be receiving the new vertices and putting them somewhere. This happens in your code, so the data isn’t hidden from you.

Display lists are better than rendering in immediate mode, but generally they are a very poor choice compared to VBOs.

Update: “Professional”-market OpenGL drivers like Quadro and FireGL will have more effort put into their display list implementation than consumer level cards. But even then the amount of optimization that they can do is much less than old-school 3D programmers from the SGI days think they get. The display list is supposed to capture state changes and other factors, but still take into consideration other states that may change independently of the display list.

It’s been a couple years since I had hard information on current driver implementations, but at point a display list would hold your geometry data in software and upload them like a plain vertex array since it may need to know certain gl states to make adjustments to the data before uploading to GPU memory. Basically, a display list gives you theoretical flexibility to make changes at execution time that it needs to know before it can upload the data. A VBO locks down the format in a way that can go straight into memory at creation time.