Since 2021.2 MSAA / Antialiasing is always OFF in WebGL

Fine in 2021.1.28, switched to 2021.2.4 and MSAA is always OFF, the value of QualitySettings.antiAliasing is NOT set to 0 but it still acted as if MSAA is disabled completely.

Just to be sure I wasn’t crazy, created an empty project in both 2021.1.28 and 2021.2.4 with a simple shape and no matter what the 2021.2 would always acted as if MSAA is disabled (extremely obvious jaggies).

Not using URP / HDPR, simply using the default renderer. On Desktop not mobile.

There’s a bug in 2021.2 that causes MSAA to appear broken, the fix is ready, just gotta get it merged in :slight_smile:

2 Likes

Excellent! Thank you!

We have the same problem. In which version will the fix be in?

The fix was a bit delayed because it required pulling in fixes to Emscripten, but is in the merge queue now and will be fixed in all affected versions (2021.2+). I can’t give an exact date/version for the fix since the merge process is variable time.

1 Like

I still see this in 2021.2.12, so I guess it’s not merged yet. Is it possible to get an ETA now ( @brendanduncan_u3d )?
Edit: also would be very helpful to have this listed under “Known Issues” in the release notes, as far as I can tell it isn’t, at least for .12 and .13.

I just saw the merge queue message this morning that it got merged into 2021.2. Sometimes that merge queue takes a while. So it should be in whenever the next update of 2021.2 is.

So a new 2021.2 version has landed, but I still can’t find anything about this under fixes or known issues. Am I missing something?

I checked and it should be working in 2021.2.14f1. The release notes were sitting in my “please verify” bin. It’s been busy.

@brendanduncan_u3d I’m sorry but MSAA still doesn’t work in 2021.2.14f1, unless you made a typo and meant the next upcoming version not yet available? 2021.2.15f1?

Please please check again, you’ll see that it still doesn’t work. This is a pretty big issue that makes webgl a no go

7952593--1018339--upload_2022-3-9_14-38-10.png

I didn’t checked 2022 yet, hopefully it was properly fixed on those version.

Just tested the latest 2022, it is properly fixed on it but definitely not on 2021.2.14f1

You’re right, sorry for (my) confusion. I tested the 2021.2 staging branch, which is working, and verified I was wrong when I said 2021.2.14f1. The staging branch is listed as 2021.2.16f1, as far as I know this will be the next release.

1 Like

Thank you so much!