Hi Neil, PagedLOD is what you need to use to balance the load for really large databases. You databases are likely to huge though, gigabytes rather than terrabytes, and the OSG' paging system allows you to scale to terrabyte database pretty comfortably so you'll do just fine is you manage the scene structure well. Doing it well is not a trivial task though so expect to be effort in learning about the issues and time experimenting with different scene graph structures.
You might also want to use some high level cull callbacks that cull subgraphs based on which room floor you are as this way you can get more effective culling. You can enclose each region with its own bounding mesh - see osgSim::VisibilityGroup for this type of culling. One thing you want to be careful about is tricks like relaxing such culling to allow the pager to start bringing in the new floor level prior to it becoming visible. Robert. On Thu, Apr 10, 2008 at 9:33 AM, <[EMAIL PROTECTED]> wrote: > Hi All, > > Not sure if I've got the correct title for this question, but hopefully > the forum might be able to help. > > Suppose that I wish to model a complete office in OSG. The office is on > two floors, the downstairs split into many rooms, the upstairs open plan. > Desks, computers, windows, doors and everything that you would find in an > office needs to be modelled, down to the pencil on the desk and the clutter > in the corner. > > Resource wise we are talking potentially a few thousand models, each with > two LOD's, all with highly detailed, high resolution textures, and many many > facets. In fact the design is so big that I can't load it all into memory. > > What are my options ? > > My client won't accept any delay in transiting from one area of a design > to the next. So multiple design files for the individual areas seems a non > starter, unless someone can tell me how I could do this without a delay > moving from one area to the next. Some form of preemptive loading springs to > mind, but is there an existing mechanism within OSG for handling that sort > of thing ? > > My thoughts led to the database pager, but I haven't used this at all, and > would hate to start looking at it only to find a few weeks later that it > really isn't suitable for my needs. > > Can anyone suggest an approach given the constraints please ? > > Many thanks > > Neil. > > > > _______________________________________________ > 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
