Hi Robert, >> Curious. >> What happens when makeCurrent runs from the same thread? What happens on a relaseContext?
In both cases, nothing; it seems to be created only on first "attachment" to it (i.e. only for the first wglMakeCurrent() for each thread). Doing stopThreading() and startThreading() triggers it since the threads are shutdown and new ones spawned, creating new worker threads in the NVIDIA OpenGL DLL. >> As a general note I don't expect users to be stopping and starting threads too often in apps. The threading model handler in osgviewer.cpp is something that useful for >> experimentation but you won't find such a handler is most users apps, I expect them to start them app and only occasionally open and close windows. >> The but with this is that single thread multiple window usage forces the viewer to do lots of makeCurent, releaseContext pairs, so each frame we could be talking about >> pushing this issue. I will check that out, but as mentioned above this should not create an issue, since the new OpenGL-worker thread seems to appear only on the first wglMakeCurrent() done by new graphic threads. If the OSG graphics thread remains the same, then this should not be a problem. But I need to double-check that. André _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
