[osg-users] DatabasePager frezzing fps

Robert Osfield robert.osfield at gmail.com
Mon Jun 1 05:22:05 PDT 2015

Hi Leandro,

On 1 June 2015 at 13:04, Leandro Linardos <leandro.linardos at gmail.com> wrote:
> Yes, definitely 1024x1024 is a huge tile size. I'm working with a CDB (Common Database) database, and the tile size is 1024x1024 by definition.
> Subsampling (using sampleRatio
>  in osgTerrain::Terrain) improve the performance.
> Once merged, the LOD switch in the PagedLOD it's ok, no freezing. Some hints or ideas to fix the merging freeze keeping the tile size?

The 1024x1024 is the problem, while it might be what the database
format you have uses, it's not appropriate for real-time work.

One workaround would be to generate multiple TerrainTile tiles for
each CDB tile.

Another approach would be to try the DisplacementMappingTechnique in
OSG svn/trunk and recent dev releases.  This technique downloads the
tile elevations as a texture and then uses shaders to place a shader
base geometry to the correct elevations.  This shared geometry is
created once per LOD level and once per Latitude for geocentric
databases.  The memory footprint with DisplacementMappingTechnique is
substantially lower.


More information about the osg-users mailing list