Hi Micahel, It could be a big with the GLCompileVisitor not cleaning up on the state it's compiling. Could you create a small example that illustrates this problem - such as modifiying one the OSG examples such as osgshape so it can reproduce the error. With such an example I can then step through what is being set and work out what might be going on, and what needs to be done to address the issue.
Robert. On 22 January 2014 10:33, Michael Bach Jensen <[email protected]> wrote: > Hi, > > During development of a new shader-based point-rendering system I started > getting "INVALID_OPERATION at start of State::apply(StateSet*)" for the > first rendered frame (subsequent frames are OK). > > The scene consists of a geode, shapedrawable box (no stateset/fixed > function pipeline) and the point rendering node (shader pipeline) both > under the same parent group. When rendering, the box is drawn before the > points. > > It turned out to be due to my point shader being active for the box. The > shader becomes active (by mistake?) as a result of the renderer calling > compile(). > > Adding a stateset to the box node with an empty program fixes the issue > since it forces fixed function into effect before drawing the box. > > It would be nice to avoid this initial INVALID_OPERATION message. > > Has anyone else encountered this or something similar? It looks like a bug > to me. What do you think? > > Thank you! > > Cheers, > Michael > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=57951#57951 > > > > > > _______________________________________________ > 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
