Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.1.X
Votes
0
Found in
2021.3.6f1
2022.1.9f1
2022.2.0b1
2023.1.0a2
Issue ID
UUM-10505
Regression
No
Google Chrome 103 does not load UI Image when using Linear color space on the WebGL platform in a full-screen mode
To reproduce:
1. Open the project “My project”
2. File → Build Settings → WebGL → Switch Platform
3. In the same window, Player Settings → Color Space → Linear
4. Build the project and open the application in Google Chrome (103 version)
5. Notice the square in the middle of the screen
6. Enter full-screen mode
Expected result: The square is still visible
Actual result: The square is not visible
Reproducible with: 2021.3.6f1, 2022.1.9f1, 2022.2.0b1, 2023.1.0a2
Could not test with: 2020.3.37f1 (Package errors)
Reproduced on: Windows 10
Not reproduced on: macOS 12.4
Notes:
- Works fine with Gama Color Space
- Works fine in Google Chrome 102 version
- The problem doesn't exist on computers that do not support Linear mode
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
Chrome, specifically it's WebGL library ANGLE, has a bug related to the initialization of depth render textures. We've been working with Google to find a fix for the issue on the Chrome side. The public Chrome bug report is https://bugs.chromium.org/p/angleproject/issues/detail?id=7678.
Resolution Note (2023.1.X):
Chrome, specifically it's WebGL library ANGLE, has a bug related to the initialization of depth render textures. We've been working with Google to find a fix for the issue on the Chrome side. The public Chrome bug report is https://bugs.chromium.org/p/angleproject/issues/detail?id=7678.