Re: [osg-users] conflict with non-OSG OpenGL view?

Hi Cory, On Fri, Aug 20, 2010 at 6:56 PM, Cory Riddell wrote: > Our application is a multiple document application meaning that more > than one "document" can be open simultaneously. If I have two OSG views, > each running in their own threads, will I have the same problem? Do I > need a mutex so

Re: [osg-users] conflict with non-OSG OpenGL view?

Thanks Robert. That sounds right to me. Our application is a multiple document application meaning that more than one "document" can be open simultaneously. If I have two OSG views, each running in their own threads, will I have the same problem? Do I need a mutex so that only one frame() method

Re: [osg-users] conflict with non-OSG OpenGL view?

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

[osg-users] conflict with non-OSG OpenGL view?

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 GraphicsWin