Re: [Algorithms] VIPM, VDPM, ROAM questions

[Lucas A. <ack...@wp...>]

my 2c is that VIPM doesn't really allow for mesh modification 
(because of fixed collapse order), which is definetly doable in 
ROAM (local edit & error update).

> 2. I am trying to play around with terrain generators (seems like a
> lot of newbies often begin here).  I think I like the idea of VIPM or
> VDPM when it comes to terrains b/c you are not restricted to height
> fields and can have overhangs and caves and the likes.   Which makes
> me lean away from ROAM.  But what am I going to give up going V*PM
> over ROAM?  

fyi, as noted in the original ROAM paper, in evaluation criteria #12, 
"Although our motivating application and implimentation focuses on 
terrain (in the form of a height field), ROAM's mesh structure applies 
to manifolds of arbitrary genus with boundary."

ROAM can be, and is (at LLNL for example), used for arbitrary 
multires geometry CLOD.  it is not a trivial extension, but it makes 
ROAM extremely flexible.

-Lucas