I''m interested in seeing what method everyone uses for their terrain engine... The one''s I know of: -Roam (billion different versions) -Adaptive Quad Trees -Just throw it at the video card solution (broken into tristrips and have static lod) Everyone should vote (that has implemented these before) on whice one they think is best...if I missed any please just say you use that method ----------------------------------------------------------- "People who usualy use the word pedantic usualy are pedantic!"-me

I just throw it at the video card, but thats cause I''m lazy :-)

Roam cannot be the best, cause I never heard of it !

AQT HAS GOT to be the BEST solution, cause I wrote a terrain renderer using quad trees !

static lod and tougher videocard cannot work well, cause if it did, my Quad Tree would be useless, which it cant, since I''ve spent 6 weeks writing it !



Seriously, Quad Trees are nice, cause :

- very fast culling, by eliminating a whole subtree in just one check.

- can easily reduce the number of triangles by a factor of 10

- it is very suitable for scaling detail depending on machine. Its as simple as changing a detail treshold to change the rendering detail.

How have you not heard of ROAM? I hear Quad trees are very t&l friendly, but I''ve never implemented one so I would know...keep em comming people!

-----------------------------------------------------------
"People who usualy use the word pedantic usualy are pedantic!"-me

Quadtrees - cos I''m trying to write a quadtree engine at the moment and it is challenging. Think B&W uses a form of Quadtrees and that looks lush.



---

Fleejay

yes it does