Re: [Algorithms] Terrain performance comparrisons

[Pierre T. <p.t...@wa...>]

> I'm personally in the Chunked-LOD camp myself. It's flexible,
> easy-to-implement and speedy. The only problem I can foresee with the
> algorithm is that I think using a dynamic dataset (ala TreadMarks) may not
> be feasible. I haven't played around with it much myself, so there's not
> much to back that statement up with other than mere speculation. I think
it
> would be possible to use a dynamic dataset, but it would probably require
a
> rather heavily modified implementation of the algorithm. This is though,
as
> I said, mere speculation.

I would be interested to hear more opinions about this (esp. Thatcher's one,
of course). I need a dynamic terrain for a project. Time is short. I'm a bit
familiar with Thatcher's chunk-LOD implementation, but maybe not enough to
imagine all required modifications.

It looks like it's possible since the code already performs vertex-morphing
all the time, but maybe I'm missing one or two difficulties.

Pierre