**** Post for FREE via your newsreader at post.usenet.com ****

Hi,
   I am writing this opengl program, wherein I render a lot of 
Quad_strips . The rendering is slow. So, I am thinking of using display 
lists.  A friend of mine was telling me about Vertex Arrays. Which one 
would be better in terms of performance.

What are the considerations we need to make, when we go in favour of one 
of them.

- Srini.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
                      http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Hi,

correct me,but i think display lists are compiled (half/rendered?) once and
then only called to screen. vertex arrays hold the data to render your
quads but they are rendered each time you call them... so displaylists are
faster. you cannot change a vertex without compiling the dlist all over
though
hope i could help
matthias
ps look at nehe.gamedev.net ... it's all there...

Matthias Edelhoff wrote:
> Hi,
> 
> correct me,but i think display lists are compiled (half/rendered?) once and
> then only called to screen. vertex arrays hold the data to render your
> quads but they are rendered each time you call them... so displaylists are
> faster.

Display lists can be faster but your reasoning is
totally wrong.

With a display list, your driver may be smart enough
to store the vertex data on the graphics card, making
it much faster to process than a vertex array which is
in main RAM.

On the other hand, there are extensions to store vertex
arrays on the graphics card ("Vertex buffer objects")
and the advantage disappears.


> you cannot change a vertex without compiling the dlist
 > all over though

That's the big difference. A display list cannot be changed,
a vertex array can.


-- 
<\___/>          "To err is human, to moo bovine."
/ O O \
\_____/  FTB.    For email, remove my socks.