# OpenGL Can't seem to render to FBO

## Recommended Posts

I've gotten render-to-texture working multiple times in the past fairly easily but for some reason I can't seem to get it working now. I'm attempting to simply clear a texture attached to a framebuffer to the color green and then blit it to the screen (which has been cleared to red). Here is my code (besides window creation and glew, these are the only OpenGL calls in the entire program):

(note: I actually reconstructed this code from a glIntercept log since I don't have the code on me at the moment, but the actual code is essentially identical)
[source]

// generate framebuffer
GLuint fbo;
glGenFramebuffers(1, &fbo);
// bind it
glBindFramebuffer(GL_FRAMEBUFFER, fbo);

// generate a texture
GLuint tex;
glGenTextures(1, &tex);
glBindTexture(GL_TEXTURE_2D, tex);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, 512, 512, 0, GL_RGBA, GL_UNSIGNED_BYTE, NULL);
glBindTexture(GL_TEXTURE_2D, 0);

// attach the texture to the framebuffer
glFramebufferTexture2D(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0, GL_TEXTURE_2D, tex, 0);
// check the framebuffer's status
Log::info() << (glCheckFramebufferStatus(GL_FRAMEBUFFER) == GL_FRAMEBUFFER_COMPLETE);

// bind the frame buffer for drawing
glBindFramebuffer(GL_FRAMEBUFFER, fbo);
// draw to color attachment 0
GLuint buf = GL_COLOR_ATTACHMENT0;
glDrawBuffers(1, &buf);
// set the drawing viewport to the size of the texture
glViewport(0,0,512,512);
// clear the framebuffer to green
glClearColor(0.0f, 1.0f, 0.0f, 1.0f);
glClear(GL_COLOR_BUFFER_BIT);

// bind the default framebuffer for drawing
glBindFramebuffer(GL_FRAMEBUFFER, 0);
// bind our framebuffer for reading
// read from color attachment 0
// draw to the back buffer
glDrawBuffer(GL_BACK);
// set the viewport to the window size
glViewport(0,0,800,600);
// clear the back buffer to red
glClearColor(1.000000,0.000000,0.000000,1.000000);
glClear(GL_COLOR_BUFFER_BIT);
// blit our framebuffer to the screen
glBlitFramebuffer(0, 0, 512, 512, 0, 0, 512, 512, GL_COLOR_BUFFER_BIT, GL_NEAREST);

// clean up resources
glDeleteTextures(1, &tex);
glDeleteFramebuffers(1, &fbo);
[/source]
Obviously I wouldn't actually want to create and destroy a texture/framebuffer each frame but that's just for testing purposes. The desired result would be a green portion of the screen (the framebuffer) drawn over a red portion of the screen (the backbuffer). However, instead of green, the blitted framebuffer is appearing black, which means it hasn't been cleared. Here is what I have so far determined:

- There are no OpenGL errors being generated - I have checked glGetError() after every call, and also used glIntercept, and no errors are being detected.
- I'm getting GL_FRAMEBUFFER_COMPLETE from glCheckFramebufferStatus().
- If I initialize the texture with some data (e.g. a solid color), that color appears when blitting, indicating that the texture is being set up correctly (at least for being displayed) and the blitting works
- Since blitting works, this means that I am successfully: binding the FBO to GL_READ_FRAMEBUFFER, binding the texture to GL_COLOR_ATTACHMENT0, setting the read buffer to GL_COLOR_ATTACHMENT0, and setting the draw buffer to GL_BACK.
- If I [i]manually[/i] update the texture using glTexSubImage2D() each frame, I can see the results of that when blitting.
- I'm successfully clearing the [i]backbuffer[/i] to red - this means that glClear() is working properly.

So the problem must be with either: binding the FBO for drawing, attaching the texture for drawing, or setting the draw buffers (glDrawBuffers()).

Can anyone see anything I'm doing wrong?

EDIT: or even let me know if there's nothing wrong with it, as then I could be more sure that the problem lies elsewhere (though I'm not sure how that could be since these are the only OpenGL calls).

##### Share on other sites
I'm sorry to bump, but I've literally been trying to solve this for weeks (something as simple as rendering to an FBO? really?) with no luck whatsoever. I've isolated this code in a separate project to ensure no other code was interfering but that didn't help. I also tried copying other FBO tutorials and those don't work either! However, the difference is that I'm using glBlitFramebuffer, whereas the other tutorials are just rendering quads. (I haven't tried quads yet but I'd prefer blitting as it seems much cleaner.)

Now here's something interesting. If I insert a glReadPixels call after clearing the FBO [i]while the FBO is still bound[/i] it works! What this suggests is that the framebuffer blit operation doesn't wait until previous GL calls have finished - it is immediately called before glClear() has actually been executed on the GPU. However, inserting glFinish() and glFlush() after clearing does [i]not[/i] work - I don't see the result of the clear operation. What could this indicate? Does anyone have any information on glBlitFramebuffer that might be related?

EDIT: Hmm... inserting Sleep(1000) in place of glReadPixels also does not work. So it seems that the problem isn't that glBlitFramebuffer is being called too [i]soon.[/i] It seems that the glClear is only actually executed if I call glReadPixels on the buffer. This has me baffled... I'll mess around some more with it but if anyone has any suggestions it would be really helpful.

## 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

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627657
• Total Posts
2978472
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
Thank you in advance!
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 12
• 22
• 13
• 33