Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X
Votes
0
Found in
2017.4.1f1
Issue ID
1046256
Regression
No
[Mobile] Setting Camera.AllowMSAA = false has no effect on QualitySettings.antiAliasing
Steps to reproduce:
1. Open QA attached project
2. Build to device
3. Press 'Enable/Disable AA'
Expected behaviour: Visual quality dropping from 8x to the visual fidelity of 0x AA because MSAA is disabled
Actual behaviour: Setting Camera.AllowMSAA = false; is ignored and AA doesn't change
Reproduced on: . 2017.4.5f1, 2018.1.4f1, 2018.2.0b7, 2018.3.0a1
Not reproduced in: Editor, Windows and Mac builds
DUT Reproduced on:
iPhone 6S iOS 11.0
VLNQA00016, Samsung Galaxy S4 Mini (GT-I9195), 4.4.2, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 305
VLNQA00031, Lge Nexus 5 (Nexus 5), 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00025, Xiaomi Mi 5s (MI 5s), 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Note: It is possible to change AA level at runtime by changing QualitySettings.antiAliasing = x (and essentially disable by setting it to 0) but disabling AA from the camera doesn't work.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
trenthm
Dec 29, 2018 16:47
Actually, it looks like allowMSAA does indeed disable/enable MSAA, but the shader I was using doesn't play nicely with allowMSAA as of 2018.3, and made it seem like MSAA wasn't changing.
trenthm
Dec 28, 2018 22:39
NOT FIXED – I'm getting this same thing in 2018.3
Changing QualitySettings.antiAliasing from 0 to 4 (my desired level) causes a black flicker, so QualitySettings.antiAliasing is not an effective workaround.