Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

Jackthemeangiant

Arn't display lists supposed to be faster?

This topic is 5926 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I just implemented quadtrees in my terrain engine. At first I was using compiled display lists in each node, but that was taking up alot of memory, so I just tried rendering using a nested for loop on the fly. And I was suprised that I got much higher frame rate using the 2 for loops, opposed to the display lists. I was just wondering why this was, because I thought display lists were supposed to be faster. Thanks, Jack

Share this post


Link to post
Share on other sites
Advertisement
Display list are faster for static data, the emphsis being on static. You build them once and then use them repeatedly. The list need to be large enough to get any great benifits from them also, might be that your nodes contain too few polygons.

Share this post


Link to post
Share on other sites
Thanks for the reply.

The smallest node has 128 polygons in it. So that is why it is slower?

Is there any other methods I can use to speed it up? There has to be something faster the repeated double for loops every update.

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!