SoftShadows turn MeshStandardMaterial yellow on Pixel 3
See original GitHub issueDescription of the problem
I assume this is a driver bug on the Pixel 3, and it’s probably long-standing; it repros on dev, as well as r112 and r110. I haven’t tried any more versions. Try this fiddle; normally it’s just a white sphere:
But on Pixel 3, specifically with this line enabled:
renderer.shadowMap.type = THREE.PCFSoftShadowMap;
We get yellow:
Three.js version
- Dev
- r112
- …
Browser
- All of them
- Chrome
- Firefox
- Internet Explorer
OS
- All of them
- Windows
- macOS
- Linux
- Android
- iOS
Hardware Requirements (graphics card, VR Device, …)
Pixel 3
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Change your screen color at night on a Pixel phone
Automatically darken your phone's background & apps · Open your phone's Settings app. · Tap Display and then Dark theme. · Tap Schedule....
Read more >Yellow tint on Pixel 4a SOLVED! : r/GooglePixel - Reddit
It's not just yellow, its more like washed out. If I kept my phone locked and unused for a few hours, it'll turn...
Read more >Is the Pixel's display TOO yellow? - YouTube
There have been reports of a " yellow tint" issue on the Pixel 4a, but is it actually true? And does the Pixel...
Read more >Pixel 3: First 10 Things to Do! - YouTube
This isn't our Google Pixel 3 review, but it will give you the first set of tips and tricks to run through just...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Honestly, it seems like that softShadow function could be more efficient anyway; I’ll see if I can refactor it and fix this in the process.
Yeah, that’s what I was thinking too. I’m testing with a different example, but I’m finding if I either remove this line and return either
a
orb
instead, it starts working. Or instead I can fix it by commenting out 3 or more of these lines.Maybe just hitting some complexity limit that confuses the driver?