Hi Boon Wah, Have a look at the on screen stats between the two datasets, there will be a difference, in particular with the number of vertices per tiles, and perhaps even the number of tiles as osgdem has a default limit of tile 64x64 for height fields and 256x256 for texels so when you introduce the DEM's it may be the DEM's that limits the number of tiles.
In general one wouldn't expect the initial load time to be high on any paged database, normally it's very fast indeed and not really noticeable. So please tell us just what time to load you are seeing. Robert. On 28 August 2012 18:02, Boon Wah <[email protected]> wrote: > Hi, > > I am a user of osgDEM and used this to generate a terrain database. > > When the terrain data is first loaded by osgViewer, there would be an > initial load time. I am trying to reduce this load time drastically. > > I prepared two sets of terrain database for comparison of the initial > load time. The first set has a flat terrain (i.e. all vertices have height z > = 0) and the second set has uneven terrain (i.e. different vertices have > different heights). Both database uses the same texture and have been > compiled with osgDEM with the same parameters, with the exception the second > set was provided with a DEM map. > > What I have found out is that the first set initial load time is much > faster (more than 10x) than the second set. Why is this so, even the size of > the textures and the number of vertices remain the same for the 2 sets? > > > Thank you! > > Cheers, > Boon Wah > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=49641#49641 > > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
