Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4.15f1
2020.2
Issue ID
1265867
Regression
No
[WebGL] Distant SwiftShader mipmaps are rendered black when using Chromium browsers without hardware acceleration
Reproduction steps:
1. Open the attached project ("case_1265867-gridtest.zip")
2. Open the repro scene ("gridtest")
3. Make a WebGL build
4. Open iChrome or Edge browser and disable hardware acceleration
5. Run the build inside that browser
Expected result: Grid mipmap is rendered all the way to the horizon
Actual result: Grid becomes black after a certain distance
Reproducible with: 2018.4.26f1, 2019.4.7f1, 2020.1.2f1, 2020.2.0a20
Tested with: Chrome (84.0.4147.105), Firefox (79.0), Edge (84.0.522.52)
Notes:
1. The issue does not reproduce when hardware acceleration is turned on
2. The issue does not reproduce on Firefox even when the hardware acceleration is turned off
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Unfortunately this is a bug in Chrome rather than Unity. We will contact Google regarding this, but closing as WontFix in Unity side.
https://bugs.chromium.org/p/chromium/issues/detail?id=1114039