Hi Alan, osgsequence is working for me. Could you explain your exact steps in recreating the problem in osgsequence so that others can reproduce the problem. If we can get others to reproduce the problem then hopefully we'll be able to see a pattern emerge that can help use home in on what the problem is.
W.r.t state needing to be dirtied, this isn't relevant to osg::Sequence as it doesn't have an state, it's just a self contain node, that only affects traversal of the scene graph, not any OpenGL state. Robert. On Wed, Oct 22, 2008 at 6:04 PM, Alan Ott <[EMAIL PROTECTED]> wrote: > Hello, > > First, I'd like to say Thank You to Robert, Simba, and Chris Denham for > helping me with my last problem with the DatabasePager. Chris's suggestion > worked great. > > I just recently upgraded from OSG 2.4 to 2.6 because I needed multisample > support for my FrameBuffer Objects. When I did this, everything worked fine > execpt for two things which may be related. The first was with osgEphemeris, > and I found someone in an archive who was able to fix that problem by making > sure that the computed sky texture was marked dirty() when changed. Robert > said on the list that it "[had] been relying upon an inefficiency in the > osg::Texture2D::setImage() method that has now been fixed, so only really > worked previously by fluke." This leads me to believe that maybe more > efficiency changes were made between OSG 2.4 and 2.6 which could be causing > my next problem. > > The second problem I have is that none of my Sequences seem to work right. I > tried a lot of things outside OSG to make it work, and eventually did a diff > on the OSG 2.4 version of osg/Sequence.cpp and the OSG 2.6 version to find > out that they are identical. > > The problem goes like this. When I load a model with an Sequence in it, the > sequence runs one time. I cannot restart it ever. If I load the model, then > find the sequence node and stop it before it's drawn, I can never start the > sequence. This worked great in OSG 2.4. > > So I built the osgsequence example in 2.4 and 2.6, and as I suspected, the > 2.4 version of osgsequence works great, but the 2.6 version does not. > > I'm not sure what the problem is, since like I said, Sequence.cpp hasn't > changed at all. My suspicion is that, like the osgEphemeris problem > described above, something in 2.6 has been fixed so that it requires > notification of a change of state in the Sequence (something like a dirty() > being called?). Of course this is only suspicion, and I have not been able > to debug it very well. I'm hoping someone who knows the code better than I > do will be able to find the problem quickly. > > So I guess that's it. I think that if the osgsequence example could be made > to work, that my sequence problems would be fixed. > > Thanks for all your help, and again, thank you for Open Scene Graph, > > Alan. > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
