>OSG does "lazy" state updates (only changes an OpenGL state when needed). Therefore, if you change the OpenGL state directly (with your pure OpenGL code) then you have to inform OSG that you have done this. Otherwise OSG will assume the state is as it left it and things will get screwed up. There are functions in osg::State (I think) that allow you to inform OSG what state changes you have made. Another way is to use glPushAttribute/glPopAttribute around your code so that the state changes you make are put back when you're done.
Kind of as I suspected then. I just have to get to it and rewrite more code. Thanks for the reply. Werner. _______________________________________________ Werner Lindgård, Programmerer Telephone +47 67 81 70 00 Direct line +47 67 81 70 68 [EMAIL PROTECTED] ViaNova Systems AS Leif Tronstads Plass 4, P.O.Box 434 N-1302 Sandvika, Norway ________________________________________________ http://www.vianova.no http://www.novapoint.com ________________________________________________ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
