The OSG's database pager only loads in what is required for the
current view frustum. For paged databases you'd typically overload
your computers memory capacity if you attempted to load the whole
paged database at one time. The whole architecture of
PagedLOD/DatabasePager is built around hitting a solid 60Hz when
rendering massive databases that are otherwise too large to fit in
You can adjust how the many tiles are loaded in at runtime by setting
the viewer's master Camera's LODScale parameter, it defaults to 1.0
which is the what should work well for visuals on properly built paged
databases. You could adjust this to so that higher res tiles are
paged in and then rendered but it increases the memory footprint so is
a trade off.
Within there isn't a specific routine written to load all tiles, you
can write this yourself if you wish, it won't be difficult. but it's
not a general rendering task so out with the scope of the core OSG.
For this type of task it'll be very specific to the needs of the
particular end users.
The big question that I would have, and one you should yourself ask,
exactly what do you want all the names? Has it anything to do with
rendering? What you are trying to achieve in the end will determine
how best to do it.
On 8 September 2016 at 09:07, Zhou Shuangshuang <> wrote:
My problem is，when loading the rootnode，we often use codes like "osg::ref_ptr <osg::Node> rootnode = osgDB::readNodeFile("terrain.ive")".
My model "terrain.ive" has 8 levels, but actually osg will only load 4 levels at the beginning.
Is there any method that can load all the tiles of each levels or just load these tiles' name, for instance, just load the level n, x coordinate and y coordinate ?
Read this topic online here:
Post generated by Mail2Forum