Advertisement Jump to content


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


Terrain types...

This topic is 6873 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

Hey everyone! I''ve been doing a little research into those wonderful things called terrain engines, and thought that the wonderful people in NeHeLandTM would have valuable opinions on the subject... In terms of a data structure to store the terrain, has anyone found anything more efficient than a quadtree? I like the quadtree because you can easily rip out triangle fans for speed, but I am open to thoughts/suggestions. Are you interested in SETEC ASTRONOMY?

Share this post

Link to post
Share on other sites
That is actually pretty much as fast as its going to get because quad trees are fast. There are fancier ways of doing it like graphs and or using an area of an array, accessing it by using a position matrix. This almost makes hidden surface removal for (out of possible range of view) not nessessary, but you can possibly find a way to incorporate this in to the method you are already using. If I am not explaining this very well, don''t worry. Your method is actually good enough in my opinion. Since graphics is what normally slows programs down the most, trying to prevent polygons from being going through rasterization and some other rendering steps is most crutial.

Share this post

Link to post
Share on other sites

  • Advertisement

Important Information

By using, you agree to our community Guidelines, Terms of Use, and Privacy Policy. is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!