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
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 Pag
Hi Richard,
On Wed, Nov 25, 2009 at 9:49 AM, Schmidt, Richard
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 should be
> a commo
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 model-i
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 {}
and
Robert Osfield wrote:
> Another possibility of how to tackle adding the proxy node would be to
> use the new support (in svn/trunk) in osgDB::Options for providing a
> custom ReadFileCallback. Using this you can override the way that
> objects are loaded. PagedLOD has now has a _databaseOptions f
6 matches
Mail list logo
