Okay, I thought you meant each tile had a constant placeholder behind it at the next lowest-res level. Anyway, I can't just have these or even the lowest res tiles always on because I have to way to guarantee that my low-res geometry won't protrude through my high-res geometry in some places.
And now that I think of it, isn't there a bad visual artifact when the load wait causes you to switch from, say, level 4 to level 0 to level 5? That would be almost as bad as seeing a temporary hole in the terrain. Also, Robert, I looked at osgbluemarble just now. It looks like it is saving tiles that contain PagedLOD nodes. I am using tiles generated by another source and don't have to option to put PagedLOD nodes in them. - Terry
Terry, You wouldn't need to have all your data except the highest resolution tile, only the lowest resolution one to act as a constant placeholder. In my app, I have tiles of data that have ~5 levels of detail each, I load the lowest resolution tile up front very quickly and stick it in the scene graph as the first child in a PagedLOD. The other subsequent tiles I just set up by specifying the filename, bounds and range, and they are paged in automatically. The lowest level of detail is hidden automatically when the higher resolution pages in. Jason -----Original Message----- From: [EMAIL PROTECTED] on behalf of Terry Welsh Sent: Tue 1/9/2007 4:12 PM To: [email protected] Subject: Re: [osg-users] PageLOD holes > > Message: 7 > Date: Tue, 9 Jan 2007 13:10:33 -0500 > From: "Jason Beverage" <[EMAIL PROTECTED]> > Subject: RE: [osg-users] PageLOD holes > To: "osg users" <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > > Hi Terry, > > I haven't been following this thread very closely, but is your essential > problem that things look correct until the pager needs to load > something, resulting in a hole until the data is finally loaded? That's correct. > > You can get around this by having adding the lowest level of detail > loaded directly into the scene graph as the first child in your PagedLOD > using addChild. It will stay there at all times, and ensure that > *something* is always displayed, even when paging. I've used a similar > approach on my project and it works really well. I gave this some thought after Robert suggested it a while ago. 2 problems, though. The first is that this would require me to have all my data except for the highest level loaded at all times, which defeats the purpose of paging. The second is that I don't see any way to turn these tiles off after the high-res tiles are loaded. > > Thanks, > > Jason >
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
