Hi Wojtek,
Problem affects DrawArrays with TriangleStrips and TriangleFans as
primitives. Also happens when DrawArrays are precompiled into display
lists. Apllication must be run multithreaded with main thread doing
window / GL context setup and worker thread doing OpenGL rendering.
Problem
wglMakeCurrent per frame should not be necessary, and can be expensive. If
this is submitted as a change to OSG, please ensure it is only enabled for
the affected platforms/configurations, and not enabled where it is not
needed.
-Paul
___
osg-users
Hi Wojciech,
On Fri, May 9, 2008 at 2:16 PM, Wojciech Lewandowski
[EMAIL PROTECTED] wrote:
Problem could be relaxed when wglMakeCurrent gets called before each frame
rendering. I noticed that artifacts appeared when wglMakeCurrent was called
only once while worker rendering thread
Hi J-S,
Wow, nice sleuthing Mr. Holmes :-) Any chance you could devise a patch we
could test, and see if it has a large adverse impact on performance?
Thanks. I will see what I can do. It might be a bit difficult because OSG
precompiles display lists on a first frame. I suspect that OpenGL
Hi Wojtek,
As far as I know you did not see this under Vista. This particular bug
shows only in XP.
Indeed, you remember correctly.
Btw. Can you check another piece of code ie: my modified prerender bug
repro ? This might be related to threading handler problems you
reported. I have posted
Hi Robert, Paul and J-S,
I don't think I was clear enough. Its too early to say that wglMakeCurrent
will be a good workaround for OSG.
I only said that it relaxed the problem in my OpenGL repro.
It looks like first wglMakeCurrent (when renderer thread is started) does
not initialize properly
Thanks, a lot
Red frame should never happen. I change flag color to red at the begining of
update callback and change it to green at the end of this callback. You have
seen red then you just confirmed that there is a bug in OSG or OpenThreads.
And update callback might get called at the same
Wojciech Lewandowski wrote:
Thanks, a lot
Red frame should never happen. I change flag color to red at the
begining of update callback and change it to green at the end of this
callback. You have seen red then you just confirmed that there is a
bug in OSG or OpenThreads. And update callback
Paul Melis schrieb:
When I run your modified osgprerender example the red flag is shown
the first second, after that it turns to green and stays that way.
This is on a dual-core Linux system with nVidia hardware using the
default threading model. If I set the threading model to single
Paul Melis wrote:
Wojciech Lewandowski wrote:
Thanks, a lot
Red frame should never happen. I change flag color to red at the
begining of update callback and change it to green at the end of this
callback. You have seen red then you just confirmed that there is a
bug in OSG or OpenThreads.
Thanks for testing Everyone.
This shows that problem is wider and not limited to windows. It looks like
GL objects visitor in Renderer thread started by Viewer:: Realize may ovelap
with first updateTraversal. I guess its turn for Robert move ;-)
Cheers,
Wojtek Lewandowski
On Fri, May 9, 2008 at 4:09 PM, Wojciech Lewandowski
[EMAIL PROTECTED] wrote:
Thanks for testing Everyone.
This shows that problem is wider and not limited to windows. It looks like
GL objects visitor in Renderer thread started by Viewer:: Realize may ovelap
with first updateTraversal. I
Paul Melis wrote:
Paul Melis wrote:
Wojciech Lewandowski wrote:
Thanks, a lot
Red frame should never happen. I change flag color to red at the
begining of update callback and change it to green at the end of
this callback. You have seen red then you just confirmed that there
is a bug in
Hi Wojtek,
This shows that problem is wider and not limited to windows. It looks like
GL objects visitor in Renderer thread started by Viewer:: Realize may ovelap
with first updateTraversal. I guess its turn for Robert move ;-)
I just booted up my Ubuntu partition, and I can confirm what
14 matches
Mail list logo
