Hi Richard, Interesting bug... fixing it is likely to be a bit awkward given the currently implementation of ProxyNode/DatabasePager, doing one file at a time won't even address all the potential issues as the ordering can sit get out of sync if early children fail to load but later children succeed. Adding support into DatabasePager to allow it to set specific children would require osg::Group to support having null children, something which has quite a few potential pitfalls.
My first thought for a solution would be to change ProxyNode so that is only has one filename, rather than multiple ones as it has now. This would avoid any issues about which files are loaded and keep the filename list in sync with the children. This is an API change though, but I can't see a better option right now. Thoughts? Robert. On Wed, Mar 24, 2010 at 1:25 PM, Schmidt, Richard <richard.schm...@eads.com> wrote: > Hi, > > there seems to be an error using proxyNodes. If you setup a proxyNode using > multiple filenames, not all files may get paged in correctly. > > This is related to the sequence the databasepager loads nodes, which may > vary if you load nodes using curl. There is no association between the > filename and the node which gets paged in, so the proxyNode, request may > request nodes twice. > > > > Possible solution: > > Let ProxyNode::traverse only request one Node at a time. If the file is not > found however, the follow up filenames will never be requested. > > > > Regards, > > Richard > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
