• 9
• 9
• 10
• 9
• 10
• ### Similar Content

• By lxjk
Hi guys,
There are many ways to do light culling in tile-based shading. I've been playing with this idea for a while, and just want to throw it out there.
Because tile frustums are general small compared to light radius, I tried using cone test to reduce false positives introduced by commonly used sphere-frustum test.
On top of that, I use distance to camera rather than depth for near/far test (aka. sliced by spheres).
This method can be naturally extended to clustered light culling as well.
The following image shows the general ideas

Performance-wise I get around 15% improvement over sphere-frustum test. You can also see how a single light performs as the following: from left to right (1) standard rendering of a point light; then tiles passed the test of (2) sphere-frustum test; (3) cone test; (4) spherical-sliced cone test

I put the details in my blog post (https://lxjk.github.io/2018/03/25/Improve-Tile-based-Light-Culling-with-Spherical-sliced-Cone.html), GLSL source code included!

Eric

• Good evening everyone!

I was wondering if there is something equivalent of  GL_NV_blend_equation_advanced for AMD?
Basically I'm trying to find more compatible version of it.

Thank you!

• Hello guys,

How do I know? Why does wavefront not show for me?
I already checked I have non errors yet.

And my download (mega.nz) should it is original but I tried no success...
- Add blend source and png file here I have tried tried,.....

PS: Why is our community not active? I wait very longer. Stop to lie me!
Thanks !

• I wasn't sure if this would be the right place for a topic like this so sorry if it isn't.
I'm currently working on a project for Uni using FreeGLUT to make a simple solar system simulation. I've got to the point where I've implemented all the planets and have used a Scene Graph to link them all together. The issue I'm having with now though is basically the planets and moons orbit correctly at their own orbit speeds.
I'm not really experienced with using matrices for stuff like this so It's likely why I can't figure out how exactly to get it working. This is where I'm applying the transformation matrices, as well as pushing and popping them. This is within the Render function that every planet including the sun and moons will have and run.
if (tag != "Sun") { glRotatef(orbitAngle, orbitRotation.X, orbitRotation.Y, orbitRotation.Z); } glPushMatrix(); glTranslatef(position.X, position.Y, position.Z); glRotatef(rotationAngle, rotation.X, rotation.Y, rotation.Z); glScalef(scale.X, scale.Y, scale.Z); glDrawElements(GL_TRIANGLES, mesh->indiceCount, GL_UNSIGNED_SHORT, mesh->indices); if (tag != "Sun") { glPopMatrix(); } The "If(tag != "Sun")" parts are my attempts are getting the planets to orbit correctly though it likely isn't the way I'm meant to be doing it. So I was wondering if someone would be able to help me? As I really don't have an idea on what I would do to get it working. Using the if statement is truthfully the closest I've got to it working but there are still weird effects like the planets orbiting faster then they should depending on the number of planets actually be updated/rendered.

• Hello everyone,
I have problem with texture

# OpenGL Can't render depth cubemap OpenGL

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

## Recommended Posts

I'm trying to render a shadow cubemap but I'm getting a black texture. I tried to look for an answer but most of the answers I found seem to be either including an unnecessary color attachment or the issue is with the projection of the shadow map. I got it to work for 2D images (dir + spot lights) but not point lights due to this issue.

Here is my Framebuffer generation code:

glGenFramebuffers(1, &fbo);
glBindFramebuffer(GL_FRAMEBUFFER, fbo);

glDrawBuffer(GL_NONE);

glGenTextures(1, &depthBuffer);
glBindTexture(GL_TEXTURE_CUBE_MAP, depthBuffer);
for (size_t i = 0; i < 6; i++) {
glTexImage2D(GL_TEXTURE_CUBE_MAP_POSITIVE_X + (GLenum)i, 0, GL_DEPTH_COMPONENT32, width, height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, NULL);
}

glTexParameteri(GL_TEXTURE_CUBE_MAP, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_CUBE_MAP, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_CUBE_MAP, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE);
glTexParameteri(GL_TEXTURE_CUBE_MAP, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE);
glTexParameteri(GL_TEXTURE_CUBE_MAP, GL_TEXTURE_WRAP_R, GL_CLAMP_TO_EDGE);

glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthBuffer, 0);

GLenum status = glCheckFramebufferStatus(GL_FRAMEBUFFER);
if (status != GL_FRAMEBUFFER_COMPLETE) {
fprintf(stderr, "Framebuffer Error. Status 0x%x\n", status);
}

// Unbind
glBindFramebuffer(GL_DRAW_FRAMEBUFFER, 0);

Here is my shadow map rendering code run for each view. I don't use geometry shaders to automatically swap between the views because right now I'm trying to support everything starting 3.1 (I have a decent PC but my old laptop only supports that.) I may support both paths based on performance later:

glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo);
for (size_t j = 0; j < 6; j++) {
glFramebufferTexture2D(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_TEXTURE_CUBE_MAP_POSITIVE_X + j, depthBuffer, 0);
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
geometryCache->Draw(proj, view[j]);
}
glBindFramebuffer(GL_DRAW_FRAMEBUFFER, 0);

And finally, I render the deferred rendering sphere for the point light including this:

...
glActiveTexture(GL_TEXTURE4);
glBindTexture(GL_TEXTURE_2D, depthBuffer);
glBindFramebuffer(GL_DRAW_FRAMEBUFFER, 0);
...

Does anyone have any ideas? Also, is it better to use gl_FragDepth to manually define the depth or to use a blank fragment shader for shadow maps (both spotlight and pointlight? Thanks in advance!

##### Share on other sites

Not sure of the answer though have noticed your rendering 6 times, once for each face.

Not too dificult to modify the tutorial for multiple lighting with a texture array.

Edited by paulgriffiths

##### Share on other sites

Not sure of the answer though have noticed your rendering 6 times, once for each face.

Not too dificult to modify the tutorial for multiple lighting with a texture array.

Hey, thanks Paul, but I already saw that link. I did say: "I don't use geometry shaders to automatically swap between the views because right now I'm trying to support everything starting 3.1 (I have a decent PC but my old laptop only supports that.)"

##### Share on other sites

I don't see any mention of PCF, perhaps force a compare mode of none to fix the black texture issue.

glTexParameteri(GL_TEXTURE..., GL_TEXTURE_COMPARE_MODE, GL_NONE);

##### Share on other sites

I don't see any mention of PCF, perhaps force a compare mode of none to fix the black texture issue.

glTexParameteri(GL_TEXTURE..., GL_TEXTURE_COMPARE_MODE, GL_NONE);

I'm not using PCF on point lights until I get it to work at all :P Also I tried COMPARE_MODE before I posted, it didn't work.

##### Share on other sites

For my old shadows with debug depth texture displayed in corner, I had the same side effect which toggling the parameter (re-gen) would workaround. Though it wasn't the first or last time GL gave empty results of course!

For your second question I think there's nothing to lose by using an empty frag shader. Though I can't say the same for the alternative. I think the difference (if any) is readablity in your code. Best to test on various machines if you can, but I think optimizes like that are secondary and driver dependent.

##### Share on other sites

For my old shadows with debug depth texture displayed in corner, I had the same side effect which toggling the parameter (re-gen) would workaround. Though it wasn't the first or last time GL gave empty results of course!

I'm sorry, toggling which parameter? Compare_mode?

For your second question I think there's nothing to lose by using an empty frag shader. Though I can't say the same for the alternative. I think the difference (if any) is readablity in your code. Best to test on various machines if you can, but I think optimizes like that are secondary and driver dependent.

Alright fair point, I'll keep that in mind. I just didn't want to do too many tests when the answers are probably already known.

##### Share on other sites

For my old shadows with debug depth texture displayed in corner, I had the same side effect which toggling the parameter (re-gen) would workaround. Though it wasn't the first or last time GL gave empty results of course!

I'm sorry, toggling which parameter? Compare_mode?

...

Yes. GL_NONE would be set (when generating the

texture) for displaying the debug quad. Or enable a compare mode for normal shadow lookups to work. I noticed nobody else seemed to have the issue and later searched images for one which displayed a shadowed scene plus debug at the same time. Guess my method was old as the issue happened way back in 2008!

Also, not at work PC right now but I think you should set parameters before generating textures, possibly within the cube loop? I forget tbh.

##### Share on other sites

Before this thread gets too old, plus if the OP is still around, and certainly for search results: I suspect the OP is using glBlitFrameBuffer from an FBO direct to the backbuffer, in which case the SRC/DST coords must be the same dimension. However, as stuff like shadow debug windows tend to be a fraction of the original size when viewed (as a 'postage stamp') then a 2nd FBO is required for the scaling to take place to. Then a 1:1 blit can be done from the 2nd FBO to the backbuffer with matching dimensions on SRC/DST.

I can't imagine why GL is like this, imo a bug :)

Edited by jezham

##### Share on other sites

Before this thread gets too old, plus if the OP is still around, and certainly for search results: I suspect the OP is using glBlitFrameBuffer from an FBO direct to the backbuffer, in which case the SRC/DST coords must be the same dimension. However, as stuff like shadow debug windows tend to be a fraction of the original size when viewed (as a 'postage stamp') then a 2nd FBO is required for the scaling to take place to. Then a 1:1 blit can be done from the 2nd FBO to the backbuffer with matching dimensions on SRC/DST.

I can't imagine why GL is like this, imo a bug :)

Looking at the documentation for glBlitFramebuffer, it states that calling the function with different source and destination rectangle sizes will use interpolation (which must be either GL_NEAREST or GL_LINEAR). Did you call it with a valid filter?

There are some notable cases to handle which can be seen in the "Errors" section:

GL_INVALID_OPERATION is generated if mask contains any of the GL_DEPTH_BUFFER_BIT or GL_STENCIL_BUFFER_BIT and filter is not GL_NEAREST.

GL_INVALID_OPERATION is generated if filter is GL_LINEAR and the read buffer contains integer data.

GL_INVALID_OPERATION is generated if GL_SAMPLE_BUFFERS for the read buffer is greater than zero and the formats of draw and read buffers are not identical, or the source and destination rectangles are not defined with the same (X0, Y0) and (X1, Y1) bounds.

Edit:

Sorry, I forgot that we were talking about multisampled FBOs - it seems like there is some strange behavior with those indeed. :)

Edited by SleekoNiko