Hi Robert et. al.,
I've tested the new vertical scale implementation on osgTerrain::Terrain
now and it works great, BUT...
The typical osgTerrain databases we would operate on are = 8GB in size
(i.e. full gtopo30 + bluemarble 500m + selected areas in higher
resolution). When altering
Hi John,
Perhaps a Terrain::init() or update() method would be appropriate -
one that goes through all the tiles registered with
the terrain and calls init() on them.
As for 16 seconds, this is looong time. I am only seeing around a
second of time update on a database
that is getting on
2 matches
Mail list logo