Hi Judson, On 28 May 2013 20:36, Judson Weissert <[email protected]> wrote: > I just got the 3.1.7 developer release built. Running the osgviewer > application with arguments "--run-on-demand --screen 1 dumptruck.osgt" > results in a regression where the viewer does not respond to mouse or > keyboard input (does not render any new frames, does not allow me to exit > via escape, does not respond to 's' for stats, etc). Similar behavior occurs > in my application, but I have not had a chance to run the code in a debugger > yet. > > Running the osgviewer application without the --run-on-demand flag appears > to work as expected. > > Compiled with Visual C++ 2010, running on Windows 7 (Same machine and > compiler settings as my previous tests).
I just tested: osgviewer --run-on-demand --screen 0 dumptruck.osgt And it worked fine. I can't test --screen 1 I don't have a second display attached right now. I wouldn't expect this to make a difference. Could you try --screen 0? Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
