Hi,
Dirk Reiners schrieb:
Hi Oliver,
On Tue, 2005-10-04 at 15:32 +0200, Oliver Kutter wrote:
Hi,
I get a strange warning, when I run my application:
WARNING: Window::frameExit: Caught stray OpenGL error invalid value (0x501).
WARNING: Rerun with debug-libraries to get more accurate information.
When I rotate my application to a certain angle / position, this warning
appears. It disappears, when I go on with rotating.
I can't find the reason why this happens!
As the message implies, this is just a fallback catcher that I put into
the Window a little while ago. In Debug mode OpenSG tests the OpenGL
state for errors quite a lot, but that can have performance
implications, which is why it's not done in Opt mode. That it only
appears in some views indicates that it's a problem with the material of
one or a few objects.
OpenGL errors can most easily happen when you pass the wrong enum value
to one of the state setting functions. As there is only one enum type
for all functions, that can happen very quickly (do you need to use
GL_LINE, GL_LINES, GL_LINE_TOKEN or GL_LINE_BIT for turning on wireframe
in glPolygonMode?). The best way to catch this is to run your program
through an OpenGL logger that tests every OpenGL command for errors. I
use bugle on Linux, and there are a bunch of them for Windows like
glIntercept or glRemedy's gDebugger. That will show you the exact
command causing the problem, and with that either you can see it already
or I can give you a better idea of what's going wrong.
I found out something. For my particle and streamline visualization I
use GL_TRIANGLES primitives as particles and GL_LINE_STRIP as
streamlines. Now I have added, that the particle geometry can be changed
to GL_POINTS (and re-create the whole geometry). And I use the
FBOViewport for computation of the particles (ehhm, it should, in the
near future ;-) ). Anyway, the error comes around, when I change to
GL_POINTS and at the same time use the FBOViewport, the error does not
come with GL_TRIANGLES and without FBOViewport. Sometimes, the error
changes to
WARNING: Error in Texture-Creation!
but the texture of the FBOViewport is ok (I created a plane and put the
texture on it, where I can see it).
funny thing, isn't it.
bye
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
