hm, i just randomly came across this issue: microsoft/vcpkg#20650 .. is vcpkg maintained really that poorly? this is the third bug breaking
--head builds in the last month
Hi guys, I'm attempting to implement a billboard text effect with background but I can't get it right.
To avoid z-fighting, I set the Text part to 1 in stencil buffer and draw the background when not equal to 1 so it will ignore the Text part.
To avoid z-fighting, I set the Text part to 1 in stencil buffer and draw the background when not equal to 1 so it will ignore the Text part.
But the effect is like this cause all the text are set to 1 in stencil buffer so all the background objects will just ignore it.I wonder how to solve the problem or if there's a better solution to implement it.
for (auto& iprGroup : _iprDisplayGroup[step]) {
GL::Renderer::setStencilFunction(GL::Renderer::StencilFunction::Always, 1, 0xff);
GL::Renderer::setStencilMask(0xff);
// Draw Text
auto& textRenderer = iprGroup.textRenderer;
if (textRenderer) {
textRenderer->finish(_camera.camera().cameraMatrix());
_camera.camera().draw(textRenderer->getDrawable());
}
}
for (auto& iprGroup : _iprDisplayGroup[step]) {
GL::Renderer::setStencilFunction(GL::Renderer::StencilFunction::NotEqual, 1, 0xff);
GL::Renderer::setStencilMask(0x00);
// Draw Diamond Background
_camera.camera().draw(iprGroup.upIprBgGroup);
// Draw Background Outline
_camera.camera().draw(iprGroup.upIprOutlineGroup);
// Draw Line
_camera.camera().draw(iprGroup.upIprLineGroup);
}
@Azvf instead of fighting with the depth/stencil buffer, the usual way to do this is with the "painter algorithm", from back to front ... or, in your case, basically ensuring the text gets always drawn after its associated background and outline, but before any other backgrounds
draw call order affects the result, yes -- there's no sorting by depth per-se, only that the fragments drawn later get discarded if they fail the depth test (or, vice versa, if the fragment "in the back" would be drawn first, the fragment "in the front" would overwrite it if drawn later, instead of the fragment "in the back" getting discarded)
argh webgl!!!
- i need to detect ANGLE in order to add a workaround for its bug
- but there's no way to detect it from the vendor/renderer string because they mask the info away to avoid fingerprinting
- fortunately, there's WEBGL_debug_renderer_info that can give me the "unmasked" info
- HOWEVER, latest Firefox seems to be printing a warning every time it gets used: https://issueexplorer.com/issue/ruffle-rs/ruffle/5279
or if the shapes are always on top anyway, then it's enough to disable the depth test altogether when drawing them, and then enable it again after
I tried the mothod of disabling the depth test a few days ago but the result is not good looking so I still attempted to render them as normal object using depth test. It's my first time doing this so I wonder if there's a common practice that can render the scene properly when many layers are in the same position.
Hi at all. I think there is something strange on iOS. Every time you call the
@mosra Am I missing something? Thanks in advance!
mapForDraw method, that framebuffer become useless. It just renders a black screen on it. I'm currently using the 2020.06 version of Magnum. This happens even on the simple triangle example! Infact, the object picking example does render a black screen on iOS.@mosra Am I missing something? Thanks in advance!
the vanilla unchanged object picking example renders a black screen?
It works on Android and Windows, but not on iOS (both Simulator and real device iOS 15)
Both
maxDrawBuffers and maxColorAttachments return 8. I can't understand why.
But the strange thing is... take a look at this:
http://vec3f.github.io/2014/09/15/deferred-shading-part-1/
He is NOT using
http://vec3f.github.io/2014/09/15/deferred-shading-part-1/
He is NOT using
layout qualifier, but he use out vec4 fragColor[3];, where 3 is the amount of render targets...
does anything improve if you call
Now I try this in a moment... I have to switch to macOS.
Even though I use the
GL::Framebuffer::ColorAttachment{my_index_here} in my own code...
but i'd suppose it's equivalent and the location is implicit (0, 1, 2) that way? would need to check the GLSL spec
does anything improve if you call
GL::defaultFramebuffer.mapForDraw({Shaders::Phong::ColorOutput, GL::DefaultFramebuffer::ColorAttachment::Back});(or a variant of it that actually compiles) right before the blit call?
I think you wanted this, right?
GL::defaultFramebuffer.mapForDraw({{MyShader::ColorOutput, GL::DefaultFramebuffer::DrawAttachment::Back}});Because I cannot find GL::DefaultFramebuffer::ColorAttachment::Back nor in the docs (last version), nor in 2020.06.
Anyway, always black output in that framebuffer.
sigh
you'd only see that in Xcode itself
or by checking for GL errors manually
Thanks anyway!
the OpenGL profiler tool from xcode tools are still there, you just have to look in the additional downloads webpage
Currently
AspectRatioPolicy in SceneGraph::Camera is hardcoded with default ::NotPreserved value, is this by design? Would be nice to get it as parameter or maybe configurable global default