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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
WebGL 1.0 does not support MSAA render targets, only available in WebGL 2.0