-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on android device using the latest source codes #2285
Comments
I think it may be casued by the code in view.h: COLOR_ALL combines all the color buffer like COLOR0 | COLOR1 | COLOR2 | COLOR3 |
Full stacktrace for the crash: |
@pixelflinger Mathias, looks like the assert might be too strict when we want to clear FBO 0. That or we should be careful to clear only |
And we found another issue related to clear process. When we render model into a rendertarget,it seams filament not clear the color buffer of render target ,in despite we call view.setClearTarget(true,true,true) |
@geroge-d can you file another issue for the clear error, and please give us as much info as possible. |
we now always mask out target bits that don't exist in the render target before converting them to GLenums. Fixes #2285
we now always mask out target bits that don't exist in the render target before converting them to GLenums. Fixes #2285
Hi guys
I built a debug version using the latest source codes, and ran into a crash
Crash log below:
/Filament: KHR_debug PERFORMANCE: Tracking surface compression isn't performant when decompressing just for an app read
../../filament/backend/src/opengl/OpenGLDriver.cpp:1988: GLsizei filament::OpenGLDriver::getAttachments(std::array<GLenum, 6> &, const filament::OpenGLDriver::GLRenderTarget *, filament::backend::TargetBufferFlags) const: assertion "!defaultFramebuffer" failed
The text was updated successfully, but these errors were encountered: