[osg-users] How should I organize the scene graph to handle 2 million points and lines?
aburnettthompson at googlemail.com
Tue Nov 3 12:49:56 PST 2009
Sorry to butt in the conversation here, but I also am working on an app with
memory issues and we are considering Paged LOD.
For a scene with millions of objects, won't there be a huge performance hit
as geometry is loaded/unloaded?
I imagine the sort of scene like a city scape where detail is controlled
very nicely. That's good as occlusion means not too many things will be
visible at any one time.
However what in the case of points and lines as the user above has posted?
Surely in this case loads will be visible at once, there will be no
occlusion, and if you sweep around with the camera, literally thousands of
objects will get paged in/out?
Or am I being a complete noob and interpreting the way PagedLOD works?
On Tue, Nov 3, 2009 at 8:36 PM, Angus Lau <angus.lau at safe.com> wrote:
> Thank you for both of your help. It seems that PagedLOD is what I need to
> use to reduce CPU memory usage. I have tried to use PagedLOD briefly before,
> but I am not clear how I can make PagedLOD unload the unused child nodes
> once those child nodes are loaded. It seems that my PagedLOD nodes do not
> remove the nodes once it creates the child nodes. Could you please give me
> some explanation about the proper way of using it??
> Thank you!
> Read this topic online here:
> osg-users mailing list
> osg-users at lists.openscenegraph.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the osg-users