Search Issue Tracker
Fixed
Votes
0
Found in
2019.3.0a11
2019.3.13f1
2020.1
Issue ID
1248848
Regression
Yes
[WebGL] Build has lower resolution than compared to Editor
Reproduction steps:
1. Open the attached project ("case_1248848-Sortie.zip")
2. Open the repro scene ("Demo")
3. Enter Play Mode and inspect the graphics inside Game window
4. Switch build target to WebGL
5. Make a WebGL build and run it
6. Compare the graphics in the player with graphics inside the Editor
Expected result: Build resolution matches Editor resolution
Actual result: Build graphics quality is noticeably worse than in the Editor
Reproducible with: 2019.3.0a11, 2019.4.0f1, 2020.1.0a4
Not reproducible with: 2018.4.23f1, 2019.3.0a10, 2020.1.0a5, 2020.2.0a14
Tested with: Chrome (83.0.4103.97), Firefox (77.0.1), Edge (83.0.478.45)
Note: Maximizing build fixes the issue (graphics remains being fixed after minimizing, too)
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
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Resolution Note:
Fixed in 2020.1.0a5 and above.