Hi,
I hit the same problem with code ported from 1.2 to 2.0, and to trace it
I used gDebugger ( the trial ) and set breakpoints to OpenGL errors.
In my case it turned out to be using osg::Program without any shaders
for some parts of the scene.
I'll try this way also, see if it confirms the
Subject: [osg-users] Debugging Warning: detected OpenGL error 'invalid value'
after RenderBin::draw(, )
Hello Robert,
I remember you mentioning a way (in OSG) to find out the source of the message
Warning: detected OpenGL error 'invalid value' after RenderBin::draw(,)
sometime in the past
Hi J-S,
I think calling the following might be what you are looking for to
narrow down the source of your error.
pState-setCheckForGLErrors
(osg::State::CheckForGLErrors::ONCE_PER_ATTRIBUTE)
where pState is a pointer to the osg::State.
Hope this helps,
Mike
Jean-Sébastien Guay wrote:
This was Robert's response to a similar situation:
---
Its likely that some OpenGL state you are setting isn't supported on
your hardware. The big question is what OpenGL features are causing
this problem. You could enable finer grained checking for OpenGL errros
via
Hello Joel,
We received this error message whenever our thread tried to update the state
of a node while the drawing thread was trying to render it. Adding a mutex
solved our issue.
Hmmm, I'm doing this in the update traversal, so I should be ok on
that front... But maybe I'll test it out
Hello again,
We received this error message whenever our thread tried to update the state
of a node while the drawing thread was trying to render it. Adding a mutex
solved our issue.
Hmmm, I'm doing this in the update traversal, so I should be ok on
that front... But maybe I'll test it out
6 matches
Mail list logo
