Re: [osg-users] SingleThreaded leading to whole application just running on one core

Hi Robert, > Have you tried setting the affinity of the threads that are created? > Have you tried creating the threads before the call to viewer.realize()? Yes, both cause the threads being distributed across the cores. That is probably also why initialising TBB early in main helps, as it

Re: [osg-users] SingleThreaded leading to whole application just running on one core

Hi, I can confirm the behaviour with the following test case: https://github.com/fwiesel/vertexarrayfunctest/blob/threads/main.cpp#L92-L103 All threads run on CPU 0. That clears up the mystery, which baffled me and two of my colleagues: After upgrading to a new Ubuntu version, suddenly our

Re: [osg-users] SingleThreaded leading to whole application just running on one core

Hi, > OSG is setting the affinity for some of its own threads, which is totally > legitimate. Currently, I was not able to confirm it on my Mac. But I think, I observed such a behaviour in my application on Linux. But take it with a grain of salt, as it can be the result of some other side

[osg-users] Lazy Disabling without VertexFuncsAvailable

Hi, I have converted my fixed function OSG program to a shader pipeline (using setVertexAttribArray and shaders instead of the setVertexPointer et al) and did run into some issues when disabling "UseVertexAttributeAliasing", and OSG is compiled with OPENGL_PROFILE=GLCORE (So