Hi Hagen, It does sounds like paging would help you out - as it'll manage the loading of only visible items automatically. Creating a PagedLOD based database would allow you to keep you app simple, with no need for trying to be clever about picking what parts to load - it'll all come free as part of osgViewer.
Robert. On Tue, Aug 19, 2008 at 2:57 PM, Kaiser, Hagen <[EMAIL PROTECTED]> wrote: > @paul: Yes indeed. Thank you for the tip. > > @Robert: > In my Application I have rooms and fixed camera-positions. > The Data I load in this application constist of loaded IVE-Files. > Every loaded node is a single object, but is composed by some subnodes i > dont care about. > Because Im loading many many files the loading time takes too much > So my decision was to make a preprocessing step. > I once load all Objects in a room. Then I look whether the object is > visible from a camera-viewpoint. > I mark them in our database. > The next time I try to load a "Camera-Viewpoint" I don't have to load > all the objects in the room but only the visible objects. > So I can speedup loading. > > If I would want to write a custom visitor I need to get this polytope > somehow out of the actual cam-parameters and the do some manual testing. > Do you have some hints for that? > > Greetings > Hagen > > > _______________________________________________ > 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
