Sign in to follow this  


Recommended Posts

irreversible    2862
I've been at this for hours and IMO my code looks pretty clear-cut. Nevertheless, I'm obviously missing something because two things are happening that I'm unable to explain:

1) first off, I'm trying to blur my shadowmap cascades (I'm using four)
2) my source is a four-layer float 32 GL_TEXTURE_2D_ARRAY RGB target (call it [i]texVSM[/i]), which is updated properly in the VSM projective phase
3) [b]Peculiarity 1[/b]: for some reason my VSM FBO requires me to bind the target array ([i]texVSM[/i]) to a texture (input) although no texture look-ups are being done inside the shader (it just calculates the moments and stores them in the active slice); if I don't bind the texture, the depth buffer is updated, but the color attachment ([i]texVSM[/i]) is not. As usual, I'm selecting my output slice by calling:

[i]glFramebufferTextureLayerEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT + iIndex, iHandle, 0, iLayerIndex);[/i]

I'm relatively sure you don't need to bind a texture for it to work as an FBO attachment.

4) rendering shadows as-is at this point works nicely (save for the first peculiarity)
5) my second FBO expects [i]texVSM [/i]as its input at TU 0 and writes to another 3D texture attachment (call it [i]texBlurVSM[/i]) (I've also given it a go by binding the output target as its primary input)
6) [b]Peculiarity 2[/b]: nothing is ever written to [i]texBlurVSM[/i], even if I set the shader to output a constant color. This is very weird, because the code is pretty much identical to that of the first FBO, except for the fact that it's a post-processing effect and just draws a single quad. In other words, I'm unable to copy anything from one 3D texture to another through an FBO proxy. I've disable depth testing and masking for the blur FBO and it makes no difference

At this point I'm rather out of ideas as to what to even try or change. So far I have something like 6 FBO's in use and they all work just fine save for the blur one.

Here's a stitched-together mock-up of the code I'm using for both FBOs (these calls are pseudocode for actual OpenGL calls):

fbo = CreateFBO();
fbo->AddAttachement(new Texture);
fbo->AddInputs(...); //basically adds all texture handles to the FBO's internal list for automated binding

fbo->Enable(); //updates attachments and calls glBindTexture() for all inputs (texture targets and TU's are automatically taken care of)
for(i to numCascades)
fbo->ActivateLayer(i); //calls glFramebufferTextureLayerEXT() as above for all attached output targets
//RenderShadowCasters() for the projective phase
//Draw a quad over the viewport for the blur phase

Any thoughts?

Share this post

Link to post
Share on other sites
sprite_hound    461
I think you might need a call to glDrawBuffer or glDrawBuffers, if you want to render to something other than GL_COLOR_ATTACHMENT0.

Incidentally, from what I remember of rendering to a 3d / array texture layer, the call to glFramebufferTextureLayer attaches one layer of the texture to the attachment point. So if you're only rendering to one layer at a time, you might as well use GL_COLOR_ATTACHMENT0 for all of them, instead of GL_COLOR_ATTACHMENT0 + i. (If I'm not misunderstanding what you're doing with iIndex / iLayerIndex here).

On the other hand, if you want to render to several layers at once, you should attach them all to separate attachment points once, then output multiple values from the shader (using gl_FragData or different out locations). I'm not sure what your AddAttachment(new Texture) call does -> if this is the whole 3D texture, it's not necessary, you just need to attach the individual layers. (Binding the whole 3D texture is instead used with gl_Layer in a geometry shader to render to each layer.)

Share this post

Link to post
Share on other sites
elurahu    258
Could you try and explain what's happening and why you think there's anything wrong. If you're trying to validate your results using gDebugger you would find that it simply doesn't work when it comes to layered FBOs.

Also FBO's are very VERY picky when it comes to which calls you're using and I've personally experienced different behaviors using the EXT, ARB and core calls. So try to translate the pseudocode into actual ogl calls so we have a chance to see which you're using.

Also if you're trying to render to several layeres at once do as __sprite also said - Pick a layer using a geometry shader as that's the only way atm. If you try to do that you need to bind the layered texture to the FBO using the glFramebufferTexture() call NOT the layered one as that only binds a single slice.

Share this post

Link to post
Share on other sites
irreversible    2862
Cheers for the answers!

Ugh, work never helps to reply faster; but I finally have the time to post the full code (the iterator iIndex for the attachment number is from a generic piece of code that binds any number of added attachments - it's not specific to this example). The GL code that is called is (note that I'm actually checking each and every GL FBO call for errors and doing rather strict compatibility and format/error checking, which I have removed for clarity):

//accepts an already propely created texture ref; additional error and compatibility checking is done here
void FBO:AddAttachment(TEXHANDLE tex)
int iIndex = output.size() - 1;

if(GetNumLayers(tex) > 1)
glFramebufferTexture3DEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT + iIndex, GL_TEXTURE_3D, GetHandle(tex), 0, 0)
glFramebufferTexture2DEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT + iIndex, GL_TEXTURE_2D, GetHandle(tex), 0)

void FBO:AddInput(TEXHANDLE tex)

void FBO::Enable()
//set up the target list for glDrawBuffers(); the output[] array contains refs to actual target handles

UINT iNumActiveTargets = 0;

for(UINT i = 0; i < GD_MAX_TEXTURE_UNITS; i++)
{ mrt[i] = GL_COLOR_ATTACHMENT0_EXT + i; iNumActiveTargets = i + 1; }
mrt[i] = NULL;

glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, iHandle);

glDrawBuffers(iNumActiveTargets, mrt);

for(i to numinputs)
glBindTexture(GetTarget(input[i]), GetHandle(intput[i]);

void FBO::ActivatLayer(int iLayerIndex)
glFramebufferTextureLayerEXT(GL_FRAMEBUFFER_EXT, GL_DEPTH_ATTACHMENT_EXT, iHandle, 0, iLayerIndex);
for(iIndex all attachmetns)
glFramebufferTextureLayerEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT + iIndex, iHandle, 0, iLayerIndex);

I hope there are no mistakes in the above code as I had to copy these bits together from all over the place (my code is structured in an object-oriented manner on multiple levels). I'm not including my texture generation code, which is used to actually create all the targets as it's an all-around piece of code and contains some hacks (nevertheless, I use it all over the place and it works just fine, both for 2D and 3D targets). If there's any other code I can include, please let me know; I'm guessing that, if anything, the above bit should be to blame, though.

>> (Binding the whole 3D texture is instead used with gl_Layer in a geometry shader to render to each layer.)

My Cascaded VSM store depth code uses the above method of output layer selection and works just fine; why would I need to use a geometry shader here?

Also, I'm only rendering to a single slice at once (the calling code structure in the OP loops through each layer and does the magic individually on each one)!

Or am I misunderstanding the whole thing?

Thanks for the input!

Share this post

Link to post
Share on other sites
V-man    813
If you are rendering to 1 slice at a time, then
glDrawBuffers(iNumActiveTargets, mrt);

probably needs to be
glDrawBuffers(1, mrt);

Share this post

Link to post
Share on other sites
sprite_hound    461
Your ActivateLayer function looks incomplete / wrong, you might want to check you've copied it here correctly. (You're attaching a layer of some texture as a depth attachment, then iterating something and attaching that same layer as color outputs... even if that's allowed in the specs (which seems unlikely) it doesn't make any sense).

Your enable function also appears to be adding a draw buffer for every attachment, but you say you only want to render to one attachment. I'm not sure what the specs say happens if you only output to one drawbuffer having specified several, but it may be undefined (at least for the buffers you don't output to).

(I'm not sure that putting inputs in the fbo class really makes sense from a conceptual viewpoint of what a framebuffer object actually is either?)

In the end, you appear to want to render to one output attachment at a time. That output just happens to be a layer of a 3D texture. So you want something like this:

[font="Lucida Console"][size="1"]// At startup:
Create your fbo.
Attach the depth buffer (assuming this stays constant, if not, do so at render time).

// At render time:
For each layer of 3D texture
* Attach one layer of 3D texture to COLOR_ATTACHMENT0 (using glFramebufferTextureLayer).
* Render to that layer (just output gl_FragColor).[/size]
OR something like this:

[font="Lucida Console"][size="1"]// At startup:
Create your fbo.
Attach depth buffer (assuming it's constant...)
Attach 3D texture to GL_COLOR_ATTACHMENT0 (using glFramebufferTexture).

// At render time:
Render once (use a geometry shader to output vertices once for each layer, using gl_Layer to specify which. Fragment shader outputs to gl_FragColor.)
On the other hand, if you really wanted to render to multiple attachments, your code would look something like this:

[font="Lucida Console"][size="1"]// At startup:
Create fbo.
Attach depth buffer.
Attach one layer of 3D texture to each attachment point (using glFramebufferTextureLayer).

// At render time:
Render once (Fragment shader outputs a value to each attachment using gl_FragData[n]).[/size][/font]

Share this post

Link to post
Share on other sites
irreversible    2862
V-Man - my code automatically degenerates to rendering to just one attachment if there is just one color target attached :). Generally working with 2 or more attachements made me write an FBO class that automatically takes care of any number of attached targets.


You're absolutely right - I made a mistake when copying the code. The layer activation code should be (with some more elaboration):

void FBO::ActivatLayer(int iLayerIndex)
//activate the desired layer for the depth buffer (assumed to be 3D)
glFramebufferTextureLayerEXT(GL_FRAMEBUFFER_EXT, GL_DEPTH_ATTACHMENT_EXT, iDepthHandle, 0, iLayerIndex);
//loop through all color attachments (assumed to be 3D and have the same number of layers as the depth buffer) and activate the desired layer
for(iIndex in all attachments)
glFramebufferTextureLayerEXT(GL_FRAMEBUFFER_EXT, GL_COLOR_ATTACHMENT0_EXT + iIndex, output[iIndex], 0, iLayerIndex);

[left]Which assumes the FBO has any number of color attachments and a single depth attachment, all of which have the same number of layers. The reason I'm not just activating attachment 0 is because I'm looping through all color targets and activating them to their rightful attachments at the requested layer. Again, this degenerates to what V-Man wrote if there is only one attachment. The same applies to Enable() - the code assumes the FBO can have up to GD_MAX_TEXTURE_UNITS attachments, but only enables those that have actual targets attached to them. Unless I'm blind to boot, I'm pretty sure there are no logic problems with this code.

What is especially annoying is the fact that OpenGL is generating zero errors (as mentioned in the OP, I'm actually checking each and every FBO call for errors and none are generated - I've removed the checks for clarity from the posted code). Is there any way I can check if my GTX 260M is even supposed to support this? I mean, maybe the drivers are silently letting the code slip, but there's no actual hardware support.

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 Arulbabu Donbosco
      There are studios selling applications which is just copying any 3Dgraphic content and regenerating into another new window. especially for CAVE Virtual reality experience. so that the user opens REvite or CAD or any other 3D applications and opens a model. then when the user selects the rendered window the VR application copies the 3D model information from the OpenGL window. 
      I got the clue that the VR application replaces the windows opengl32.dll file. how this is possible ... how can we copy the 3d content from the current OpenGL window.
      anyone, please help me .. how to go further... to create an application like VR CAVE. 
    • By cebugdev
      hi all,

      i am trying to build an OpenGL 2D GUI system, (yeah yeah, i know i should not be re inventing the wheel, but this is for educational and some other purpose only),
      i have built GUI system before using 2D systems such as that of HTML/JS canvas, but in 2D system, i can directly match a mouse coordinates to the actual graphic coordinates with additional computation for screen size/ratio/scale ofcourse.
      now i want to port it to OpenGL, i know that to render a 2D object in OpenGL we specify coordiantes in Clip space or use the orthographic projection, now heres what i need help about.
      1. what is the right way of rendering the GUI? is it thru drawing in clip space or switching to ortho projection?
      2. from screen coordinates (top left is 0,0 nd bottom right is width height), how can i map the mouse coordinates to OpenGL 2D so that mouse events such as button click works? In consideration ofcourse to the current screen/size dimension.
      3. when let say if the screen size/dimension is different, how to handle this? in my previous javascript 2D engine using canvas, i just have my working coordinates and then just perform the bitblk or copying my working canvas to screen canvas and scale the mouse coordinates from there, in OpenGL how to work on a multiple screen sizes (more like an OpenGL ES question).
      lastly, if you guys know any books, resources, links or tutorials that handle or discuss this, i found one with marekknows opengl game engine website but its not free,
      Just let me know. Did not have any luck finding resource in google for writing our own OpenGL GUI framework.
      IF there are no any available online, just let me know, what things do i need to look into for OpenGL and i will study them one by one to make it work.
      thank you, and looking forward to positive replies.
    • By fllwr0491
      I have a few beginner questions about tesselation that I really have no clue.
      The opengl wiki doesn't seem to talk anything about the details.
      What is the relationship between TCS layout out and TES layout in?
      How does the tesselator know how control points are organized?
          e.g. If TES input requests triangles, but TCS can output N vertices.
             What happens in this case?
      In this article,
      the isoline example TCS out=4, but TES in=isoline.
      And gl_TessCoord is only a single one.
      So which ones are the control points?
      How are tesselator building primitives?
    • By Orella
      I've been developing a 2D Engine using SFML + ImGui.
      Here you can see an image
      The editor is rendered using ImGui and the scene window is a sf::RenderTexture where I draw the GameObjects and then is converted to ImGui::Image to render it in the editor.
      Now I need to create a 3D Engine during this year in my Bachelor Degree but using SDL2 + ImGui and I want to recreate what I did with the 2D Engine. 
      I've managed to render the editor like I did in the 2D Engine using this example that comes with ImGui. 
      3D Editor preview
      But I don't know how to create an equivalent of sf::RenderTexture in SDL2, so I can draw the 3D scene there and convert it to ImGui::Image to show it in the editor.
      If you can provide code will be better. And if you want me to provide any specific code tell me.
    • By Picpenguin
      I'm new to learning OpenGL and still learning C. I'm using SDL2, glew, OpenGL 3.3, linmath and stb_image.
      I started following through and got through it until I had to load models. The problem is, it uses Assimp for loading models. Assimp is C++ and uses things I don't want in my program (boost for example) and C support doesn't seem that good.
      Things like glVertexAttribPointer and shaders are still confusing to me, but I have to start somewhere right?
      I can't seem to find any good loading/rendering tutorials or source code that is simple to use and easy to understand.
      I have tried this for over a week by myself, searching for solutions but so far no luck. With tinyobjloader-c and project that uses it, FantasyGolfSimulator, I was able to actually load the model with plain color (always the same color no matter what I do) on screen and move it around, but cannot figure out how to use textures or use its multiple textures with it.
      I don't ask much: I just want to load models with textures in them, maybe have lights affect them (directional spotlight etc). Also, some models have multiple parts and multiple textures in them, how can I handle those?
      Are there solutions anywhere?
      Thank you for your time. Sorry if this is a bit confusing, English isn't my native language
  • Popular Now