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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment