Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
1
Found in
2017.1.0b10
Issue ID
923698
Regression
Yes
No Anti-Aliasing in WebGL1.0
Steps to reproduce:
1. Download and open the user project in GitHub (https://github.com/qCring/UnityWebGLAATest)
2. Build for WebGL
3. Open "about:config" in Firefox and disable "webgl.enable-webgl2"
4. Open generated html in Firefox
5. Notice that the cube is not affected by Anti-Aliasing
Expected result: Anti-Aliasing should be present in WebGL builds
Reproduced in: 2017.2.0b2, 2017.1.0f3, 5.6.2p2, 5.6.0a2
Not reproduced in: 5.5.4p1, 5.4.5p4
Regression since: 5.6.0a2
Fixed in: 2017.3.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment