-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Teared rendering results with artifacts when blend mode is translucent #7794
Comments
Note: not sure if its strictly the fact that its using transparency or the fact that no skybox is used. The other samples work, but they all use skyboxes if I am not mistaken |
Update: In the multi-view example I was able to circumnavigate the issue by commenting out this line: Line 136 in 99eac62
So I assume it's not related to the skybox but really just to the translucent blending mode. |
I can reproduce, the problem seems to be linked to our use of the framebuffer_fetch extension on these devices. Enabling any feature that turns that off will appear to fix the problem. For instance enabling MSAA, TAA, DoF or bloom. Also disabling post-processing or color grading. This needs more investigation... |
The problem also goes away when I change our internal format from RGBA16F to RGBA8. This starts looking like a driver bug. |
Hi, we are having the same issue. Is this going to be fixed on the Filament side, or are we waiting for Pixel to fix their driver? |
Describe the bug
When rendering content with filament with transparency the image is pixelated / is torn apart / has artifacts.
In general it works, we were able to reproduce this especially on google pixel devices.
The original discussion started here:
To Reproduce
sample-transparent-view
demo on a google pixel device. We used a Pixel 7 ProExpected behavior
its rendered without tearing and artifacts.
Screenshots
IMG_7750.MOV
IMG_7749.MOV
Logs
If applicable, copy full logs from your console here. Please do not
use screenshots of logs, copy them as text, use gist or attach an uncompressed file.
Providing those in a moment, will run the sample app with the debug flags enabled.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The problem seems to be fixed on Pixel devices when either:
view->setPostProcessignEnabled(false)
(note: disabling each post processing effect doesn't fix the issue, only turning it off completely)The text was updated successfully, but these errors were encountered: