While using Filament with ANGLE on Windows (using D3D11 backend of ANGLE) we noticed getting lots of warnings like this:
OpenGL framebuffer error 0x8219 (GL_FRAMEBUFFER_UNDEFINED) in "blit" at line 3581
We use Filament v1.50.3 and there the problematic driver calls comes from here. Looking at the implementation of OpenGLDriver::blit() it seemed to me there was a bug (fix me if I am wrong). It:
binds an FBO as DRAW target then attaches images to it
checks the completeness of READ target FBO (what if there's no FBO bound as READ target?)
binds another FBO as READ target then attaches images to it
checks the completeness of DRAW target FBO (this technically works because DRAW target FBO is already configured)
I couldn't reproduce it with gltf_viewer + Windows OpenGL driver but it can be that ANGLE is more chatty on the debug output than the Windows OpenGL driver. And regardless of this, the FBO checks still seem to be mixed up
While using Filament with ANGLE on Windows (using D3D11 backend of ANGLE) we noticed getting lots of warnings like this:
We use Filament v1.50.3 and there the problematic driver calls comes from here. Looking at the implementation of
OpenGLDriver::blit()it seemed to me there was a bug (fix me if I am wrong). It:I couldn't reproduce it with gltf_viewer + Windows OpenGL driver but it can be that ANGLE is more chatty on the debug output than the Windows OpenGL driver. And regardless of this, the FBO checks still seem to be mixed up