Jump to content

View more

Image of the Day

雑魚は多めにして、爽快感重視にしつつ・・・(´・ω・`)
早いとこ、ベースを作って、完成にもっていかないとね。
タイトルもまだ迷ってるだよなぁ。 
#indiedev  #indiegame #screenshotsaturday https://t.co/IwVbswGrhe
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

Vertex Array or Display Lists...?

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
5 replies to this topic

#1 Metus   Members   

168
Like
Likes
Like

Posted 06 August 2001 - 10:13 PM

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)

#2 Julio   Members   

116
Like
Likes
Like

Posted 07 August 2001 - 01:41 AM

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.

#3 Anonymous Poster_Anonymous Poster_*   Guests   

Likes

Posted 07 August 2001 - 05:25 AM

A 256*256 unit landscape will take 65536 quads, not 16384


#4 Metus   Members   

168
Like
Likes
Like

Posted 07 August 2001 - 07:53 AM

Well..yes it does =)


#5 zedzeek   Members   

528
Like
Likes
Like

Posted 07 August 2001 - 09:18 AM

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)

#6 SirKnight   Members   

316
Like
Likes
Like

Posted 07 August 2001 - 09:35 AM

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




Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.