I can't really help on tracking down the cause of the error.
You can hide error messages by setting the Nofiy to ALWAYS, this will east all messages.
On 9/16/06,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Thanks for the responses.
Firstly, I have disabled all of my own GPU shader code. This didn't cause any change in the error.
The scene consists simply of a single object and a single terrain database. Removing the terrain database does get rid of the problem, but that also doesn't seem to help much seeing as it is a complex scene node.
The program has been set up based on the OSG examples for running FBO's, shadowing, and terrain paging. I tried to follow these examples as closely as possible when creating the scene.
I guess I am most interested in the OSG changes that could have caused this error to be found between v 1.1 and v1.2. Identical code under v1.1 doesn't show this error (99% of the time, anyway).
One peculiar thing did start to show up which might lend a clue. I am rendering the entire scene on the FBO and then using another basic GLUT node to draw a graph about performance of the app. The app saves the contents of the FBO out to bitmaps. From time to time, the screen buffer is getting saved to the bitmaps. Nothing consistent, but it does happen. I am tending to think this is related to the error but I am unsure how to narrow this down any further.
I appreciate how hard it is to debug such a vague error through email. If nothing else, how can I disable this error?
Robert Osfield < [EMAIL PROTECTED]> wrote:Hi,
The OpenGL error could be caused by many different errors in the scene graph setup so I can't really guess at what might be wrong. I'd recommend simplifying your scene and till the error goes away, then you should be better able to pin point the problem.
Also check the RTT examples like osgprerender and osgshadowtexture etc, do they produce errors too? This shouldn't produce errors, and if they do it suggest so problem with OpenGL driver support.
Robert.
On 9/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:I upgraded to OSG 1.2 today. I am now consistently getting the following error message whenever I use FBO's:
"Warning: detected OpenGL error 'invalid operation' after RenderBin::draw(,)"
I would get this occasionally (1% of the time) with v1.1 but now I am getting it EVERY time with v1.2. I assume there is something that I am doing wrong, but as I "see" no problems with the rendered scene, I was wondering what types of operations could be causing this or what I could do to attempt to track it down. Particularly, what operations would cause an error on the FBO that wouldn't cause an error for a normally rendered scene? Were there any changes to the RenderBin which would cause v1.2 to catch an error that v1.1 would not consistently catch? Any help would be appreciated!
Thanks!
Do you Yahoo!?
Get on board. You're invited to try the new Yahoo! Mail.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1ยข/min.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
