Re: [osg-users] PagedLOD/ProxyNode design discussion

Hi, got another opinion on the PagedLOD and ProxyNode topic. :-) We have been using both nodes for stuff like pseudo loaders as well and I would recommend to change the interface a little bit. There should be a common interface for all pageable nodes like: class PageingNode : public Group {}

Re: [osg-users] PagedLOD/ProxyNode design discussion

Hi Chris, I can't help but feel that you are trying to making this more complex than it needs to be. First up pre-loading a plugin to handle extensions is easy, as it's already built into the core OSG. Try -e ext which preload the plugin of the given extension. osgconv -e ModifyTerrain

Re: [osg-users] PagedLOD/ProxyNode design discussion

Hi Richard, On Wed, Nov 25, 2009 at 9:49 AM, Schmidt, Richard richard.schm...@eads.com wrote: Hi, got another opinion on the PagedLOD and ProxyNode topic. :-) We have been using both nodes for stuff like pseudo loaders as well and I would recommend to change the interface a little bit. There

Re: [osg-users] PagedLOD/ProxyNode design discussion

Robert Osfield wrote: got another opinion on the PagedLOD and ProxyNode topic. :-) We have been using both nodes for stuff like pseudo loaders as well and I would recommend to change the interface a little bit. There should be a common interface for all pageable nodes like: class PageingNode

Re: [osg-users] PagedLOD/ProxyNode design discussion

Robert Osfield wrote: I can't help but feel that you are trying to making this more complex than it needs to be. Well, not _trying_. ;) Sometimes I am through ignorance. I did not know you could force preload that way without First up pre-loading a plugin to handle extensions is easy, as