You are excused Rupert, considering you taught me to like Bowmore :-) (seems like a million years ago now).
:-) Anyways, it is certainly possible to "reset" the threading mask. It was just the fact that setupViewer() set this, and then left it locked to one core. The main thread (where setupViewer) then will have this threading mask until someone sets it to something else. As we was not aware of this in setupViewer() it took some debugging to understand why we did not get an even load balancing over our 4 cores. Everything just stuck to one of them (whichever the os decided to select for the app at startup). This was first discovered under linux but was reproducible under windows too. So it should be clearly documented as a sideeffect, or handled in some other manner. /Anders On Fri, Nov 5, 2010 at 11:11 AM, Robert Osfield <[email protected]>wrote: > On Fri, Nov 5, 2010 at 10:10 AM, Robert Osfield > <[email protected]> wrote: > > Hi Andreas, > > Ooopsss... I meant to type Anders :-) > _______________________________________________ > 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
