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
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
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
- [Quest 2] Surface shader and multi-view sampling custom textures broken in Quest 2
- Lighting Data asset is not created when baking multiple Scenes at the same time
- Performance issues when instantiating a recognizer under UnityEngine.Windows.Speech
- Build fails with "Exception: Unity.IL2CPP.Building.BuilderFailedException: Build failed with 0 successful nodes and 0 failed ones" when building the project for iOS
- [Android] .aab Build fails when using Asset Bundles
mcskinox
Dec 16, 2022 14:33
Changing the renderscale from 2 to 1 in the quality settings in the UniversalRenderPipelineAsset seemed to fix this error for me.
MaximilianPs
Jun 28, 2022 11:28
The error still here with URP in 2020.03.34.
Popping out when I try to add an icon on a custom editor window in Inspector!
edub101
May 04, 2022 13:51
This issue also occurs in Unity 2021.3 LTS version. Deleting the contents of the "script assemblies" folder did not resolve the issue for me.
ElliotB
Apr 23, 2022 20:05
Issue not fixed in 2021.3.0f1
MichaelEGA
Feb 04, 2022 21:35
Got this error upgrading to 2021.2.
I cleared it by removing the 'Script Assemblies' folder in 'your project name'/Library/ and getting unity to reload it.
SanketVaria
Jan 19, 2022 08:43
This still present in 2021.2.8
kleon
Jan 12, 2022 06:32
Same problem on 2021.2.5f1.
DEEnvironment
Dec 02, 2021 20:02
also found in 2021.2.4 URP 12x
DEEnvironment
Nov 24, 2021 14:37
also found in 2021.2.3 URP
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 ...