Vertex Array or Display Lists...?

Started by
4 comments, last by Metus 22 years, 8 months ago
In my upcomping forth release of my engine, im rendering a 256*256 unit landcape (256*256/4 16384 GLQUADS)... These units are STATIC during the whole rendering time (unless the Random Landscape Generator is activated) so my question is; Should I implement a Vertex Array or similar function to speed up things? GLvoid GenerateHeightMap() { ... ... glCopyCurrentMapIntoVertexBuffer(): } GLvoid DrawHeightmap() { glDrawHeightmapFromVertexBuffer(); } DrawHeightmap is being used every frame, and GenerateHeightmap once during the startup-sequence or when the user calls it via the RLG-Function (Random Landscape Generator)
Ethereal
Advertisement
vertex arrays couldn''t hurt, that way you could impliment a level of detail alogorithm and frustum culling and stuff like that. maybe try compiled vertex arrays for a little more speed than just vertex arrays.



How many Microsoft employees does it take to screw in a light bulb?
None, they just declare drakness as a new standard.
My HomepageSome shoot to kill, others shoot to mame. I say clear the chamber and let the lord decide. - Reno 911
A 256*256 unit landscape will take 65536 quads, not 16384
Well..yes it does =)
Ethereal
the biggest gain will be if u
break your landscape into smaller pieces
+hardware likes it better
+u can do some gross culling on the scene first (ie only send the stuff that is on the screen)
Well i know for nvidia cards that vertex arrays using VAR (vertex array range) is the fastest way of rendering. The only time its not is if you are using vertex programs (vertex shaders) and they are running in software ie. not having a geforce 3.

-SirKnight

This topic is closed to new replies.

Advertisement