Sign in to follow this  

OpenGL Updated my (nvidia) driver, now RTT is broken?

Recommended Posts

karwosts    840
In my application I'm rendering my scene into a cubemap, so I create the cubemap texture and then render the scene 6 times into the six faces. I've had this working fine for some time, but I just recently updated my driver for my NVIDIA 8800.

Now when I try to run the program with the new driver, I get GL_FRAMEBUFFER_UNSUPPORTED when I try to create my framebuffer. Anyone have any experience with this error?

for(uint side = 0;side<6;side++){
glTexImage2D(GL_TEXTURE_CUBE_MAP_POSITIVE_X+side, 0, GL_RGBA, resolution, resolution, 0, GL_RGBA, GL_UNSIGNED_BYTE, 0);
glGenerateMipmap(GL_TEXTURE_CUBE_MAP);//I don't need mipmaps, but I thought this might help my error.

GLuint framebuffer;

glm::mat4 proj = OpenGL::PerspectiveProject(90,1,1,0.1f,1000);

GLint viewport[4];

for(uint side=0;side<6;side++){
glm::mat4 view;
case 0: view = OpenGL::LookAt(glm::vec3(0,0,0),glm::vec3(1,0,0),glm::vec3(0,-1,0));break;
case 1: view = OpenGL::LookAt(glm::vec3(0,0,0),glm::vec3(-1,0,0),glm::vec3(0,-1,0));break;
case 2: view = OpenGL::LookAt(glm::vec3(0,0,0),glm::vec3(0,1,0),glm::vec3(0,0,1));break;
case 3: view = OpenGL::LookAt(glm::vec3(0,0,0),glm::vec3(0,-1,0),glm::vec3(0,0,-1));break;
case 4: view = OpenGL::LookAt(glm::vec3(0,0,0),glm::vec3(0,0,1),glm::vec3(0,-1,0));break;
case 5: view = OpenGL::LookAt(glm::vec3(0,0,0),glm::vec3(0,0,-1),glm::vec3(0,-1,0));break;


I saw this on, but I'm not sure if it applies to me. How can I tell if my texture is 'complete'? I've set the min/max filters and even called generate mipmaps.

Warning: NVIDIA's OpenGL driver has a known issue with using incomplete textures. If the texture is not texture complete, the FBO itself will be considered GL_FRAMEBUFFER_UNSUPPORTED, or will have GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT. This is a driver bug, as the OpenGL specification does not allow implementations to return either of these values simply because a texture is not yet complete. Until this is resolved in NVIDIA's drivers, it is advised to make sure that all textures have mipmap levels, and that all glTexParameteri values are properly set up for the format of the texture. For example, integral textures are not complete if the mag and min filters have any LINEAR fields.

Share this post

Link to post
Share on other sites
karwosts    840
Guess I can just put this down to a screwy driver install. Reinstalled it with driver cleaner and the problem went away. Thought something suspicious was going on when it was taking 100ms to render a simple untextured cube :)

Share this post

Link to post
Share on other sites
pcmaster    982
Hey, can you tell me what driver version is infected and what could work?
I suddenly experience similar stupid behaviour and cannot figure a working driver :( November 16, 2010 (GPU Caps show this, I guess it is 260.99, i.e. the newest one now) driver does not seem to work on both my GTS250 as 9600GSO.

Share this post

Link to post
Share on other sites
karwosts    840
Unfortunately I never found a resolution to this yet. I thought that upgrading my drivers fixed the issue, but a few days later it started creeping back up again.

What I constantly found happening was that after running my program a few times it started having all sorts of crazy problems: GL_OUT_OF_MEMORY errors everywhere, rendering SUPER slow (took 10 whole seconds to render a frame that used to render at 60fps), and these random framebuffer errors.

Its like there was some memory leak that was filling up my GPU, and once it got to the limit it stopped working, and the only solution I found was to reboot my computer, then everything would be fine for a day or two.

It seemed to work fine as long as I properly exited my program every time (manually deleted all the textures and framebuffers), but anytime my program exited uncleanly either through an exception or through abortion through the debugger it started happening again, it's like windows wasn't properly cleaning up the context when the program terminated.

Don't know if this is anything like your issue, but that's been my experience.

Share this post

Link to post
Share on other sites
AverageJoeSSU    564
yea but this has been going on now for 5 months or so... and this is a regression, something that should be easy to track down.

I have the EXACT same problem.

I have had this problem with my Quadro and posted a thread about it on here somewhere.

sucks that it still hasnt been resolved. i brought it up on nvidias website months ago as well and nobody at nvidia acknowledged the problem last time i checked, yet there are a lot of people encountering it... pretty frustrating.

Share this post

Link to post
Share on other sites
mhenschel    100
Same here. I found that killing dwm.exe on Vista helped a bit when the problem occurs. But it comes back after some time and sooner or later I have to reboot. I managed to get GLexpert running to get more info but all I could find was that all occurring errors are related to some out of memory condition. For instance when binding a FBO the first time the driver tries to allocate memory for all attached textures/renderbuffers. When this fails it returns GL_FRAMEBUFFER_UNSUPPORTED.

I'm chasing this issue for month now and didn't find anything in our code that could cause this. gDebugger shows no resource leaks and even if there were some the driver should release all resources when the application exits.

I really would like to report this to nVidia but it's nearly impossible to make a simple repro case. But since it's nearly impossible to become a registered nvidia developer nowadays I wouldn't even know how to submit it anyway. :-/

If any of you has found any solution or workaround please post it here. This is driving me crazy.

Share this post

Link to post
Share on other sites
karwosts    840
I'm sure it must be an unfixed bug in their driver. I'd suggest trying older ones unless you need the latest ones for some reason. I went back to 197.13 and haven't had any problems (yet), thought I haven't stressed it very much yet.

Share this post

Link to post
Share on other sites
mhenschel    100
I stumbled across this extension which is able to give some information about the memory as seen by the driver:

Under Vista or Win7 these values are global ones for all processes. I notices that for me these two numberse increase of time and over several restarts of the application:


I discovered that these two numbers increase when my app resizes an opengl window while it is still hidden. For instance this happened in our editor that shows the opengl window after doing the hole opengl setup and preparing the layout for all windows. This involves resizing the render window. After that the main editor window is shown. I can reproduce this with a simple example app. I have not tested yet if the is really our original problem but it's the only clue I have right now.

Here is a repro case for this in case you are still interested:
[source lang=cpp]
#pragma comment(lib, "glut32.lib")
#include "glut.h"
#include <stdio.h>


void PrintVideoMemory()
static GLint evicted=0;
GLint vidmem=0, mem_available=0, vidmem_available=0, evicted_count=0, evicted_size=0;
glGetIntegerv(GL_GPU_MEMORY_INFO_EVICTION_COUNT_NVX, &evicted_count);
glGetIntegerv(GL_GPU_MEMORY_INFO_EVICTED_MEMORY_NVX, &evicted_size);

if (evicted!=evicted_count)
printf("evicted_count=%d, evicted_size=%dkb, vidmem_available=%dkb\n",
evicted_count, evicted_size, vidmem_available);


void renderScene(void)
static bool flip=true;



if (flip)

int main(int argc, char* argv[])
glutInit(&argc, argv);
glutInitDisplayMode(GLUT_RGBA | GLUT_DOUBLE );

glutCreateWindow("resoource leak provoker");
glutHideWindow(); //comment this to make the leak disappear


return 0;

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now