Hi guys, thanks for the tipps. I also was thinking about overriding the traverse method as JS said. So in deed this is what I need. A simpler thing would be also, what Robert proposed, just to write own traverser.
However, in my case I will also have a circular dependency in the graph. So something like this: root | group A - node A | group B - group A | node B a graph structure which is not directly supported by osg, I know. In osgPPU I solved that kind of problem with a BarrierNode, which does break up the circle in the graph and setup all the pointers and traversers correctly. In the case of multiple iterations of group A rendering, it becames little bit complex then just overriding the traverse method. Calling accept() method on every child of group B will cause the traverser to be recursively called and hence will end up in stack overflow or something like this. I think, I will need to define some kind of mutex variable, which will be checked, so that the traverser can stop traversing on group B. But the traverser should be called several times, to achieve multiple rendering. Ok, I think I got the idea now. Thanks again. Cheers, Art ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=18402#18402 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
