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?
one has to call mapForDraw() and direct the draw back to the (front? back?) default framebuffer again in order to have something appearing on the screen, but that should be done there
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
Also, I think that usage of
SceneGraph::Camera::_rawProjectionMatrix declared here is redunant? Since this is the only usage of it as rhs, it can be replaced with original SceneGraph::Camera::_projectionMatrix, making SceneGraph::Camera::fixAspectRatio modify the value directly. Correct me if I'm wrong
Would be nice to get it as parameter
you mean setAspectRatioPolicy(AspectRatioPolicy)? :) if you want to have a global configurable default, easiest is to create your own subclass (you wouldn't believe how painful mutable globals sometimes are, which is why i tend to avoid them)
the
_rawProjectionMatrix is there because if you call the setAspectRatioPolicy() or setViewport(), it "bakes" _projectionMatrix from the raw one and the aspect ratio correction, and on a subsequent call it would have no way to know what the original ("raw") projection was to correct it again
ah well, i don't know ... so it's any call to mapForDraw() that breaks it and if it's not there it works?
even the implicit
.mapForDraw({{Shaders::Phong::ColorOutput, GL::Framebuffer::ColorAttachment{0}});with no other attachment breaks it?
Yes. I'm experimenting a bit, and yes. Even with only Color output in both Framebuffer and Phong shader output all black!
From the Object picking example, when I do
_color.setStorage(GL::RenderbufferFormat::RGBA8, GL::defaultFramebuffer.viewport().size()); then all rendering becomes black. Even if I delete all the mapForDraw, blit and other framebuffer setup code. I keep only the GL::defaultFramebuffer, untouched, as it comes from the main.
It could be this problem?
https://stackoverflow.com/questions/4829665/why-on-ios-is-glrenderbufferstorage-appearing-to-fail
https://stackoverflow.com/questions/4829665/why-on-ios-is-glrenderbufferstorage-appearing-to-fail
i'm on a call right now, will post a more detailed reply 30mins - 1hr later :)
and because magnum uses state tracking, for basic workflow it never even attempts to bind a framebuffer with ID 0, as the state tracker assumes it's bound by default (which it is, in cases of platforms where a default framebuffer is a thing)
thus basic examples all work, but everything breaks once you attempt to create a custom Framebuffer and attach something to it -- then it binds it, and when going back to
GL::defaultFramebuffer, it binds framebuffer with ID 0 instead of the actual custom framebuffer object iOS uses by default