Search Issue Tracker

Fixed in 2017.3.0f3

Fixed in 2018.1.X

Votes

0

Found in

2018.1.0a2

2018.1.0a3

Issue ID

967248

Regression

Yes

[AntiAliasing] "Invalid antiAliasing value (must be at least 1)" error on antiAliasing disabled

Graphics - General

-

Console spams error "Invalid antiAliasing value (must be at least 1)" when we set antialiasing to "disabled" in quality settings and then select camera in the hierarchy.

Steps to Reproduce:
1. Create a new project.
2. Go to Project Settings >> Quality Settings >> Anti Aliasing >> Disabled
3. Select MainCamera in Hierarchy.

NOTE: "Invalid antiAliasing value (must be at least 1)" error spams in the console.

Expected Result:
An error should not appear in the console.

Actual Result :
An error is thrown at selecting a camera.

Frequency:
Always

Notes:
- Appears on both Windows and OSX
- On some Window and OSX machines, it doesn't appear. (Appeared on 3 out of 4 Windows and 2 out of 3 Mac machines with the same configuration.)

Reproduced on Unity 2018.1.0a2, 2018.1.0a3

Regression on Unity 2018.1.0a2

Not reproduced on Unity 5.6.4f1,2017.1.1f1, 2017.2.0f3 , 2017.3.0b8 , 2018.1.0a1

License type: Pro

Comments (17)

  1. miron83

    Nov 18, 2021 18:32

    The same problem after updating to 2021.2.2 in a project with URP, but after playing with the settings it stopped showing up.
    Try this:
    Project Settings> Quality> Render Pipeline Resource [click to view the asset in the "project" tab and select it from there], after selecting the asset, go to the Inspector> Quality> Anti-Aliasing (MSAA)> and change it to Disable tab. Now play the game (press the play button) and turn it off after initialising (after few secounds). Then you can change the Anti-aliasing (MSAA) back to your choosing (I'm using 4x) and the error is gone - at least it worked for me ...

  2. Jamesshamy

    Nov 14, 2021 08:40

    Still there in 2021.2.2. Wasn't there in 2021.1.16 before update.

  3. Cronoo

    Nov 03, 2021 00:06

    2021.2.0f1 has this popping up also.

  4. LordCainen

    Oct 29, 2021 11:20

    This very issue appeares in the release version of 2021.2 right now.

  5. stevphie

    Oct 05, 2021 10:16

    This is haunting 2021.2b at the moment

  6. DiscoFever

    Sep 30, 2021 12:01

    Same issue 2021.2.0b12

  7. kaan0550

    Aug 10, 2021 16:41

    Same poblem appears at 2021.2.0b6

Add comment

Log in to post comment