Hi Cory, I won't be able to directly diagnose the problem but my guess is that it'll be an issue with keeping the context current. I would suggest letting one of the two sets of rendering tack complete control over the graphics context and just call the other set rendering to just do basic OpenGL calls.
Robert. On Thu, Aug 19, 2010 at 5:50 PM, Cory Riddell <[email protected]> wrote: > My application has an OSG view and a second non-OSG OpenGL view. > Occasionally, I'm getting a crash in > GraphicsWindowWin32::swapBuffersImplementation() with what looks like a > bad _hdc. The crash is an access violation due to an attempted write to 0. > > I think the relevant code is: > > void GraphicsWindowWin32::swapBuffersImplementation() > { > if (!_realized) return; > if (!::SwapBuffers(_hdc) && ::GetLastError() != 0) > { > > reportErrorForScreen("GraphicsWindowWin32::swapBuffersImplementation() - > Unable to swap display buffers", _traits->screenNum, ::GetLastError()); > } > } > > I'm not certain if this is correct because the crash is actually > happening down in the atioglxx.dll file. Does anybody know if AMD has a > public symbol server? > > I think it has something to do with OpenGL state between my two views > because the crash normally happens when I'm manipulating my non-OSG view > (and my OSG view is still drawing nonstop in its own thread). Is this a > bad thing to do? > > Cory > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
