[osg-users] Open Scene Graph 3.4.0 has bug when using two monitor setup

Wojciech Lewandowski w.p.lewandowski at gmail.com
Tue Dec 20 03:21:32 PST 2016

Hi Bruce,

Just from top of my head.

1. Check and verify if all osgXXX.dll and OpenThreads.dll are loaded from
correct installation directories. Similar errors often occur if
Debug/Release/Rev libs get mixed. VS Output pane displays all loaded DLLs
with long paths so its easy to verify if some lib was not picked from other

2. Check if Call stack does not show some crashes in Nvidia OpenGL threads.
Sometimes errors there affect the other threads which invoked OpenGL calls.
Also check NVidia Control Panel. There is Multithreaded Optimization
setting (actual names may vary a little as I am using my localized language
version and cannot check them in English). Experiment with it. Perhaps one
of the options will fix the problem.

3. I checked the version of OSG I have installed on my machine currently
(OSG 3.4.0). osgViewer does not crash with cessna in dual screen
(Window10/GTX 1080 drivers 375.95). But it is 64 bit build. So your 32 bit
results may still vary.

Wojtek Lewandowski

2016-12-20 9:16 GMT+01:00 Robert Osfield <robert.osfield at gmail.com>:

> Hi Bruce,
> On 19 December 2016 at 21:34, Bruce Clay <bclay1297 at gmail.com> wrote:
> > Robert:
> >   Just to be sure I pulled the latest git release and diffed it against
> the code I had and only found differences in commented headers.  I built
> the code as I had previously and got the same errors.  I am using the 32
> bit version of 3rd party dependencies which is not the latest posted but
> only a 64 bit version of the latest dependencies is posted and I need a 32
> bit app.
> >
> > I tried a couple of different things based on flags I saw in the cmake
> file.
> >
> > first I tried using the OSG_MULTIMONITOR_WIN32_NVIDIA_WORKAROUND flag.
> I rebuilt the entire package and ran osgViewer cessnafire.osg.  In this
> configuration, the program sometime crashed immediately with no scene
> display and other times ran fine.  It we still to unstable to leave in this
> configuration.
> I've just looked at the history of GraphicsWindowWin32.cpp, the
> OSG_MULTIMONITOR_WIN32_NVIDIA_WORKAROUND is a workaround for an NVidia
> driver bug from 8 years ago, I'd hope that it's no longer relevant...
>     https://github.com/openscenegraph/OpenSceneGraph/commit/
> 7c23951ee17ab444220220951dae16df7c691e2a
> > next I turned off the flag set in the previous step  and tried the
> BUILD_OPENTHREADS_WITH_QT flag and rebuilt the package.  With this
> configuration, osgViewer never crashed but some of the other / larger apps
> still crashed.   I can not name those that crashed or where they crashed at
> this moment because I am installing Visual Studio 2015 and the installer
> won't let me run any version of Visual Studio while it is doing a setup.
> It did still point towards a threading problem though.  I can check
> tomorrow when the install is finished.  Hope this sheds some light on the
> problem.  I will try vs2015 tomorrow as well.
> The effect of shifting the BUILD_OPENTHREADS_WITH_QT suggests a either
> that the bug is timing sensitive or the OpenThreads::Win32 implement
> is not protecting threads as it should be.  It may be worth looking at
> the differences between OSG-3.2 and 3.4 w.r.t OpenThreads, perhaps one
> of the "fixes" has actually caused a regression.
> Do you have any non NVidia or non Windows setups?
> Robert
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20161220/3a980a53/attachment-0003.htm>

More information about the osg-users mailing list