# OpenGL Beginning OpenGL question

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

## Recommended Posts

I need someone to explain exactly what this code means. I read the documentation and I am really confused. I am trying to understand some code and here is what is really throwing me for a loop. All of this Binding, and Generating is really confusing the hell out of me. I dont know whats coming or going. I am completely fluent in DirectX programming, but this OpenGL is messing with my head big time only on this. I also noticed that in OpenGL, a backbuffer is never created. Is there a default one created when this is called?
glutInitDisplayMode(GLUT_RGB | GLUT_DOUBLE | GLUT_DEPTH);
glutInitWindowSize(width, height);

Does the above code create a Render target with Red, Green, Blue and also a Depth buffer? Does it also automatically bind these for use upon glewInit(); ?

    glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);    glGenFramebuffersEXT(1, &a);// what does a reference now?    glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, a);// does this mean a now points to the backbuffer, or what ever is currently bound as a render target?     glReadBuffer(GL_COLOR_ATTACHMENT0_EXT);// does this mean that a is allowed to read from the backbuffer?    glDrawBuffer(GL_COLOR_ATTACHMENT0_EXT);// does this mean a is allowed to draw to the backbuffer?    glFramebufferTextureEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT, b, 0);// what exactly does this mean?    glFramebufferTextureEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT1_EXT, c, 0);    glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);// is this a way to unbind a render target, or is this considered the normal back buffer?    glGenFramebuffersEXT(1, &d);// here we go again with this generating stuff    glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, d);    glDrawBuffer(GL_COLOR_ATTACHMENT0_EXT);    glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);

The Genframebuffer function just dishes out unique id's? Then, you bind those ID's to a render target? Am i close here? I guess it is confusing because I never see any of these FrameBuffers defined. Their size, format, nothing. Then they are used later on in the code.

I realize this is alot of questions. I understand most of it, but a few of these I could not get a nice answer to yet.

##### Share on other sites
I'll take a stab at what I know:

Quote:
 I also noticed that in OpenGL, a backbuffer is never created. Is there a default one created when this is called?glutInitDisplayMode(GLUT_RGB | GLUT_DOUBLE | GLUT_DEPTH);glutInitWindowSize(width, height);

Yes, this sets up a basic double buffering setup (because of the GLUT_DOUBLE). At this point all draw calls will go into the back buffer, and then the swap command at the end of each frame will switch the buffers. At this point you're pretty much ready to go with rendering. Or at least you'd be ready except for ultra-modern opengl which doesn't allow you to use the default framebuffer anymore. But for most people they'll just start drawing their triangles here.

Quote:
 Does the above code create a Render target with Red, Green, Blue and also a Depth buffer?

Yes

Quote:
 Does it also automatically bind these for use upon glewInit(); ?

No I don't think so. glewInit only initializes the function pointers for the opengl extensions. These buffers should be the default binding. glew isn't a requirement for opengl, but it makes managing the extension pointers a lot easier (that's a whole 'nother topic there). But for now just call glewInit at the start and don't worry about it.

Quote:
 glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0); glGenFramebuffersEXT(1, &a);// what does a reference now?

'a' is just an id for an unused framebuffer.

Quote:
 glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, a);// does this mean a now points to the backbuffer, or what ever is currently bound as a render target?

No, the backbuffer still exists as it's own entity seperate from 'a'. A is an 'off-screen' render target. When you're binding 'a' to the GL_FRAMEBUFFER target, you're saying that you want any further operations on the GL_FRAMEBUFFER target to be applied to 'a', as opposed to say another framebuffer that you don't currently have bound.

Quote:
 glReadBuffer(GL_COLOR_ATTACHMENT0_EXT);// does this mean that a is allowed to read from the backbuffer? glDrawBuffer(GL_COLOR_ATTACHMENT0_EXT);// does this mean a is allowed to draw to the backbuffer?

No. The default to glRead/DrawBuffer is the backbuffer in a double buffering setup. This is saying 'anytime I do a read or write command, do the operations on the GL_COLOR_ATTACHMENT0 renderbuffer, not the backbuffer'. I think these might not be necessary in a modern shader pipeline, I think there's another method to map outputs of your fragment shader (glBindFragDataLocation).

Quote:
 glFramebufferTextureEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT, b, 0);// what exactly does this mean? glFramebufferTextureEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT1_EXT, c, 0);

This is attaching two color textures to the currently bound framebuffer ('a'). Then when you render to 'a' the results will be burned into these textures ('b' and 'c' are texture id's) instead of a renderbuffer. The shader picks which data goes into which attachment, so you could be burning two separate images in a single pass.

Quote:
 glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);// is this a way to unbind a render target, or is this considered the normal back buffer?

This just means 'I'm done doing things with framebuffer 'a', go back to the default framebuffer (the one provided by the windowing system that you're used to, with the frontbuffer and backbuffer attachments).

Quote:
 The Genframebuffer function just dishes out unique id's? Then, you bind those ID's to a render target? Am i close here?

Yes I think that is correct. The term 'render target' is pretty loose here, but you seem to have the right idea.

Quote:
 I guess it is confusing because I never see any of these FrameBuffers defined. Their size, format, nothing. Then they are used later on in the code.

This is probably because it is rendering into textures 'b' and 'c', which have probably had this data defined before. A framebuffer is really just a container for attachments (GL_COLOR_ATTACHMENTi, GL_DEPTH_ATTACHMENT, GL_STENCIL_ATTACHMENT), and then each of these attachments either renders into a renderbuffer (for blitting onto the screen), or a texture (for use like any other texture). If you wanted to draw into a renderbuffer you'd define the specifics with glRenderbufferStorage, which has the width/height/pixelformat arguments that you're probably looking for.

It seems overly convoluted but it's pretty flexible, for example this would allow you to, in a single pass of the pixel shader, generate 5 distinct color textures, a stencil texture, while at the same time drawing color and depth onto the screen. Don't know why you would ever need to do that, but if you wanted to you could :)

I hope I've got this mostly correct, but I think the gist of it is there. If you really want to get into the tiny details I'd pick up a 'Red Book', and it has detail about all of these functions and what they do.

One way to think about all these terms that might clarify things is to look at the typical default double buffering setup. In the default, you have:

1 Framebuffer
3 Attachments (GL_FRONT, GL_BACK, and GL_DEPTH_ATTACHMENT)
and each attachment has an associated RenderBuffer.

When you're creating a new framebuffer, it doesn't have any attachments, so that's where you add them (GL_COLOR_ATTACHMENT0 instead of GL_BACK, for example). Then for each attachment you either define a texture target or a render target (glFramebufferTexture or glFramebufferRenderbuffer).

[Edited by - karwosts on November 12, 2010 3:27:02 AM]

##### Share on other sites
Thanks. I that helped. .

• 10
• 12
• 10
• 10
• 11
• ### Similar Content

• Good Evening,
I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
I am really stucked right now because of the fundamental question:
Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on.
In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
Should I treat those debug objects as entities/components?
For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
Regards,
LifeArtist
• By QQemka
Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
Let's go:
Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
There were several more but i forgot/solved them at time of writing
• By RenanRR
Hi All,
I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
#version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);
So, some doubts:
- Why use it like that?
- Is it okay to manipulate the camera that way?
-in this way, are not the vertex's positions that changes instead of the camera?
- I need to pass MVP to all shaders of object in my scenes ?

What it seems, is that the camera stands still and the scenery that changes...
it's right?

Thank you

• Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

int rgbValue = int(textureSample.w);//4 bytes of data packed as color
// algorithm might not be correct and endianness might need switching.
vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
extractedData /= 255.0f;

• While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
Anyone has any idea .. what should I do?