Greetings, Forgot to mention that I have three hacks that fix/minimize the issue:
Hack #1: Check for duplicates when adding PagedLod to the activeLODList in FindPagedLODsVisitor. If a duplicate is found it is removed. This code helped determine if there are duplicates. Hack #2: In the Terrapage plugin TXPNode::updateScenegraph do the following: If the node being removed has a child, get it and see if it is a TXPPagedLod If the child node is a TXPPagedLod, check the tileIdentifier to see if it a lod 0 node. If the node is LOD 0, then setup the parameters such that the node will be paged out by the database pager. Note that TXPReaderWriter can be edited to add the filename for LOD 0 tiles. Hack #3: Put a check in FindPagedLODsVisitor if the PagedLod should be added to the active list. Don't add the PagedLod node to the activeLodList if it shouldn't be. This requires adding a parameter to the PagedLod node and editing the ReaderWriter to set that parameter correctly. Don't have the hacked up code ATM, but I could send it if needed(it's at work). It's pretty simple but all seems hackish. As for the orginal question, it doesn't seem that the tilemanager supports multiple cameras. I could see the LOD 0 nodes being paged in and out a lot if multiple cameras are used. This was all based on osg 2.8.1 / 2.8.2. I've just started looking at this code late this week, because it became top priority bug. If any one has any idea of how to fix the issue properly, I may be able to invest some time if others cannot. -Ryan
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
