Jump to content
  • Advertisement
Sign in to follow this  
Jacob Jingle

OpenGL OpenGL 4.2 Debug Window

This topic is 2604 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

After I installed the newest Nvidia OpenGL 4.2 drivers I started to get this warning popping up in a debug console window(Win 7):
Console opened at 06:31:55 29-Oct-11
GL_CLAMP_VERTEX_COLOR_ARB is clamped.
GL_CLAMP_FRAGMENT_COLOR_ARB is clamped.
There are 0 constants bound by this program.
Texture 0 uses an 32 bit floating point format.
Texture 0 is bound to texture target GL_TEXTURE_2D_ARRAY_EXT.[/quote]
This is really annoying because I already check for errors\warnings and output them to the debug pane of my c++ editor. Does anyone know how to turn off or surpress this new debug console?

Thx ahead of time,
JJ

Share this post


Link to post
Share on other sites
Advertisement
I have asked the same question. It is probably GLExpert output. Although it can be very useful in the development, it is quite annoying on the client's side.You haven't enabled debug_output, or there will be more performance warnings (telling you that the shaders are recompiled).

I bet that R285 has some bugs.

Share this post


Link to post
Share on other sites
I have asked the same question. It is probably GLExpert output. Although it can be very useful in the development, it is quite annoying on the client's side.You haven't enabled debug_output, or there will be more performance warnings (telling you that the shaders are recompiled).

I'm not sure, but I think I do. (I'm new to OpenGL)

Here's what I've logged from opengl debug callback:
sources = 33350, types = 33360, ids = 131218i, severities = 37191, msglog = Program/shader state performance warning: Fragment Shader is going to be recompiled because the shader key based on GL state mismatches.
GL_CLAMP_VERTEX_COLOR_ARB is clamped.
GL_CLAMP_FRAGMENT_COLOR_ARB is clamped.
There are 0 constants bound by this program.
Texture 0 uses an 32 bit floating point format.
Texture 0 is bound to texture target GL_TEXTURE_2D_ARRAY_EXT.[/quote]

The debug console window actually gives me less info. :o

I bet that R285 has some bugs.

I'm going to keep looking for fix, but I have a hunch that you're right.

Share this post


Link to post
Share on other sites
Yes, the drivers aways give the same message: "Program/shader state performance warning: Fragment Shader is going to be recompiled because the shader key based on GL state mismatches."

Maybe we are doing something wrong. :)

But I hope that someone from NV will eventually give some explanation what's going on. :rolleyes:

Share this post


Link to post
Share on other sites
I was able to get rid of the warning "GL_CLAMP_FRAGMENT_COLOR_ARB is clamped." with:
glClampColorARB(GL_CLAMP_FRAGMENT_COLOR_ARB, GL_FALSE);
But for the life of me I can't get rid ot the vertex one. :angry: What's the point of a warning if I don't know how to fix it....

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!