Search Issue Tracker
By Design
Votes
0
Found in [Package]
10.0.0-preview.26
Issue ID
1283125
Regression
No
[WebGL][URP] MSAA is not applied when in Build
How to reproduce:
1. Open the attached project's "case_1283125-Project.zip" Scene labeled "Scene"
2. Open the Game View Window
3. Zoom into the Cubes
4. Observe their edges
5. Make a WebGL build
6. Host the built WebGL Player
7. Open the Player in a browser
8. Observe the Cubes edges
Expected result: MSAA is applied and the Cubes edges are not jagged
Actual result: MSAA is not applied ant the Cubes edges are jagged
Reproducible with: 7.3.1, 7.5.1 (2019.4.12f1), 9.0.0-preview.55 (2020.1.9f1), 10.0.0-preview.26 (2020.2.0b7, 2021.1.0a1)
Couldn't test with: 2018.4.28f1 (Universal RP Package is not available)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
WebGL 1.0 does not support MSAA render targets, only available in WebGL 2.0