[osg-users] PagedLOD just keeps increasing number of LOD nodes

Robert Osfield robert.osfield at gmail.com
Tue Jul 12 22:57:57 PDT 2016

Hi Bruno,

As Nick mentioned you can set target maximum for the pager to aim for.
You use the OSG_MAX_PAGEDLOD env var to set this value or set it
directly the the DatabasePager method Nick talked about.

However. this is still just a target, it's still possible to exceed
this if your view actually requires all the PagedLOD to traversed in a
single frame the OSG will have no choice but keep all these in memory
as they are needed.  You can use the Camera::setLODScale(double)
method to get the OSG to select lower or higher LOD levels for a given
viewing distances.

If this it is the case that your view requires too many PagedLOD then
LODScale is really just a quick fix, the actual problem lies in
database, ideally you should be creating paged databases with
appropriate distance ranges to ensure that the whole system remains
balanced on your target hardware + data with default LOD scale of 1.0.


On 12 July 2016 at 22:39, Bruno Oliveira
<bruno.manata.oliveira at gmail.com> wrote:
> Hello,
> I have a scene with a point cloud, ordered in an octree.
> I have each node in a separate file, so I built a PagedLOD engine based
> renderer.
> My octree is of depth 2, with approximately 3 million points.
> I found out that this engine is consuming more memory than I expected. Hence
> I added a StatsHandler to my view, and found out that while navigating
> through my scene, that the 'LOD' number is ALWAYS increasing and never
> decreases. Does this means the PagedLOD nodes are not being deleted
> correctly?
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

More information about the osg-users mailing list