Overheating, Software Fallbacks, and FBOs

Started by
0 comments, last by V-man 12 years, 11 months ago
Hi,

I have found that when the GPU overheats, a program will switch from OpenGL rendering to a software fallback. More interestingly, I've found that there's a difference in semantics between software and hardware support.

My FBO class checks for errors after all the setup was completed (but before any render targets had been added). When rendering with GPU mode, this works fine. However, with the software fallback, I get GL_FRAMEBUFFER_UNSUPPORTED. This code is fairly robust and I've used it for years without incident--the problem only seems to occur when a software fallback takes place. I'm assuming this difference in behavior is unintentional. Does anyone know for sure?

Thanks,
-G

[size="1"]And a Unix user said rm -rf *.* and all was null and void...|There's no place like 127.0.0.1|The Application "Programmer" has unexpectedly quit. An error of type A.M. has occurred.
[size="2"]

Advertisement
Report the problem at the driver bugs forum http://www.opengl.org/discussion_boards/ubbthreads.php?ubb=postlist&Board=13&page=1
Sig: http://glhlib.sourceforge.net
an open source GLU replacement library. Much more modern than GLU.
float matrix[16], inverse_matrix[16];
glhLoadIdentityf2(matrix);
glhTranslatef2(matrix, 0.0, 0.0, 5.0);
glhRotateAboutXf2(matrix, angleInRadians);
glhScalef2(matrix, 1.0, 1.0, -1.0);
glhQuickInvertMatrixf2(matrix, inverse_matrix);
glUniformMatrix4fv(uniformLocation1, 1, FALSE, matrix);
glUniformMatrix4fv(uniformLocation2, 1, FALSE, inverse_matrix);

This topic is closed to new replies.

Advertisement