Hi Paul, On Fri, Oct 30, 2009 at 6:17 PM, Paul Martz <[email protected]> wrote: >> Oh just disable the matrix paths by setting the >> OSG_GL_MATRICES_AVAILABLE to OFF. > > Interesting. How did I screw _that_ up? If I figure out how that got flipped > the wrong way, I'll let you know. I was sure that was all disabled.
I now realise that not all glMatrix code is protected by the OSG_GL_MATRICES_AVAILABLE, and there are some code paths in SceneView that enclose glMatrix code without other code that isn't possible to support under GLES1 and GLES2 so I've just commented out the code using the #if !define(OSG_GLES1_AVAILABLE) && !defined(OSG_GLES2_AVAILABLE). For these block you'll may well want to do the same for GL3. The types of code paths that are disabled in SceneView tend to be the stencil based stereo effects. I would like to see these rewritten at a high level using the scene graph to do the work rather than low level OpenGL calls, this way we'd be able to avoid tying the code to specific GL targets. In the case of stereo code it really should be manage by slave cameras in osgViewer, so it possibly an opportunity for us to start doing this for GLES x.x and GL3.x support for these effects we're having to disable in SceneView. For the time being just disable the compilation of this problem code paths and chalk it down to something we'll need to re-implement later. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
