Hi Juan, Thanks for your insight,
> > As Robert already answered, it should be possible. > The best explanation that I have for your problem is that some thread > fails to do wglMakeCurrent (after that call fails anything that follows > is just garbage) beacuse another thread is holding the context > (according to > http://www.opengl.org/sdk/docs/man/xhtml/glXMakeCurrent.xml, that's a > programming error in GLX, so I guess the same applies in WGL). All > OpenGL calls from that thread are going to fail after that. > > If the sample code that I sent you also complains with the error message: > PixelBufferWin32::makeCurrentImplementation, wglMakeCurrent error: Die > angeforderte Ressource wird bereits verwendet > then, there is a threading error somewhere. However I can't spot it the > code I sent you and I'm afraid that's beyond my knowledge of OSG's guts. > Robert may be more insightful here. > > You can try commenting the line that changes the threading model and > replacing frame() by run() to see if it also fails. > It results in the same error if I comment out the setThreadingModel call, no matter if I use frame() or run(). Btw, I'm using osg v2.8.3. I compile Juan's code using the official libraries from http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8.3/binaries/Windows/VisualStudio8/ and as Robert said, it's working thread safe in a standard graphics window. If Robert is still reading this thread, is this a known issue with a solution or do I have to write a bug report? Greetings, Oliver ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=34291#34291 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
