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
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
- Some Prefab Source and Override content bounds are misaligned
- The Package Manager's "install packages by..." panels break when Domain Reload is triggered, and the panel is open
- Crash with multiple stack traces when leaving a docked VFX Graph open
Resolution Note:
Fixed in 2020.1.0a5 and above.