HI Max,
If you have got things working could you post the changed file to
osg-submissions, and if possible include an OpenFlight file and test
problem that reproduces the problem before so that we can reproduce
then confirm the fix. I very concerned that you fix will fix one type
of usage and
Hi,
I'm not sure if this should go on osg-submissions instead, or if it's even a
submission at all (deletion?), but simply removing line 192 (_start = _now)
fixes the problem.
The bug is that the openflight loader sets the sequence's mode to START
before it's in the scene graph, so the _start
Thanks for the responses.
I'm not sure what stopping the frame loop refers to, since something like
while(!viewer-done())
{
if (viewer-getFrameStamp()-getFrameNumber() == 500)
{
rootNode-addChild(
osgDB::readNodeFile(some_animation.flt));
}
viewer-frame();
}
would
Hi Max,
My guess is that your Viewer's SimulationTime is up and running by the
time the new model is loaded, rather than starting off at 0.0 which is
causing the problems.
The actual implementation details of osg::Sequence is something that
community members have working on over the years,
Hi Max,
Stopping the frame loop and restarting it without explictly adjusting
the simulation time to account for your frameloop stop is something
that I'd expect to cause problems - I also can't see how the OSG could
automatically catch this particular usage model.
Robert.
On Thu, Aug 7, 2008
Hi Max,
Stopping the frame loop and restarting it without explictly adjusting
the simulation time to account for your frameloop stop is something
that I'd expect to cause problems - I also can't see how the OSG could
automatically catch this particular usage model.
Robert.
On Thu, Aug 7, 2008
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Bandazian
Sent: 07 August 2008 18:26
To: osg-users@lists.openscenegraph.org
Subject: [osg-users] osg sequence timing
Hi,
I am experiencing some buggy behavior relating to loaded openflight
files containing
7 matches
Mail list logo
