-
-
Notifications
You must be signed in to change notification settings - Fork 35.3k
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
The combination of DirectionalLight and Environment Maps results in material artifacts in the Pixel 3 #19479
Comments
Could you create a jsfiddle that reproduces the issue on the device? |
Here is a jsFiddle where this problem can be reviewed: |
I've tested the fiddle on a Pixel 1 (with Android 10) and it looks like on my Desktop. So no rendering artifacts. |
We tested on two different Pixel 3's that we have in the office for development and both have this issue so it is not particular to one device. We are getting hold of a Pixel 4 and we will report the findings here. |
Yes, this is a Pixel 3 issue. I've bumped on this before. Thanks for the jsfiddle! 🙏 |
Indeed, this is a problem I'm hitting all the time now in model-viewer, since I only have a Pixel 3 to test on. I think it's very closely related to a bug I fixed a few months ago by refactoring a shadow shader: #18315. It was pretty clear the shader wasn't wrong, but any small change would make this driver bug appear or disappear. |
Does this issue still appear with Android 11? BTW: The above fiddle looks good on a Pixel 4a and Android 11. |
Description of the problem
When combining DirectionalLight and Environment Maps with GLTF models results in very noticeable surface artifacts on the 3D model when viewed on the Pixel 3
Start model with environment map and directional light:
Start model with only directional light:
Star model with only environment map:
Different model with directional light and environment map:
Three.js version
Browser
OS
Hardware Requirements (graphics card, VR Device, ...)
Problem only seen on Google Pixel 3
The device is running Android version 10
The text was updated successfully, but these errors were encountered: