I've found the Windows Nvidia drivers to be really bad about actually reporting OpenGL errors unless you create a debug context. It's possible that doing that will reveal something. You might have to tweak OSG itself to do that, though. My application creates the context with SDL2 and then connects it to OSG, so I've not had do so it with push alone.
Also, when I've wanted to know the cause of (rather than just the existence of) an error, it's been easier to do so via a debug callback than basic error checking as you get the full call stack and sometimes a descriptive error string. This page explains how to set that up with OSG: http://thermalpixel.github.io/opengl/osg/2014/02/06/gl-khr-debug-in-osg.html -- You received this message because you are subscribed to the Google Groups "OpenSceneGraph Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to osg-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osg-users/ed90cad2-ee36-4ae5-9f08-0f957d4875ca%40googlegroups.com.
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
