Normally the automatic setup is useful, but in the case of the .osg support this automatic update was forcing premature loading of imagery that wasn't necessarily, and can lead to reports of looking for files that arn't present.
29 lines
706 B
C++
29 lines
706 B
C++
|
|
#include <osgParticle/ExplosionEffect>
|
|
|
|
#include <osgDB/Registry>
|
|
#include <osgDB/Input>
|
|
#include <osgDB/Output>
|
|
|
|
bool ExplosionEffect_readLocalData(osg::Object &obj, osgDB::Input &fr);
|
|
bool ExplosionEffect_writeLocalData(const osg::Object &obj, osgDB::Output &fw);
|
|
|
|
osgDB::RegisterDotOsgWrapperProxy ExplosionEffect_Proxy
|
|
(
|
|
new osgParticle::ExplosionEffect(false),
|
|
"ExplosionEffect",
|
|
"Object Node ParticleEffect ExplosionEffect",
|
|
ExplosionEffect_readLocalData,
|
|
ExplosionEffect_writeLocalData
|
|
);
|
|
|
|
bool ExplosionEffect_readLocalData(osg::Object &, osgDB::Input &)
|
|
{
|
|
return false;
|
|
}
|
|
|
|
bool ExplosionEffect_writeLocalData(const osg::Object &, osgDB::Output &)
|
|
{
|
|
return false;
|
|
}
|