-
Notifications
You must be signed in to change notification settings - Fork 327
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
framebuffer not visible #983
Comments
I also noticed that there are two contexts from two different threads. One thread called "Renderthread", I don't know what that is. Maybe that's related to the problem. |
Hi @gapid-user (nice name!), |
This logic was added to handle cases where tracing missed the context creation. It got broken over time. Fixes: google#983
Thank you @gapid-user, So it looks like we never saw the call to There's another issue with this trace where pre-compiled shaders were not disabled. We've recently fixed an issue where this wasn't disabled by default. I'm planning on pushing out a release in the next few working days. Both of these issues should be fixed for that version. Thanks again, |
no this is from a new galaxy xcover 3 phone (model SM-G389F).. my old galaxy tab 2 doesn't get recognized at all by GAPID (in android studio it works fine) |
This logic was added to handle cases where tracing missed the context creation. It got broken over time. Fixes: #983
first error from log:
gapis: Framebuffer error: No format set (3 times)
Then a bunch of command errors
The text was updated successfully, but these errors were encountered: