Search Issue Tracker
Fixed in 5.0.X
Votes
5
Found in
4.2.0f4
Issue ID
558620
Regression
Yes
Changing anti aliasing during the runtime works incorrectly
The GUI Text fades or completely disappears after the anti aliasing is changed during the runtime.
Tested devices:
Samsung Galaxy S IV (GT-i9505) with Android 4.2.2
Unity Version:
4.3.0b1 (2f830c2bcd47)
Comments (2)
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
p3dart-es
Feb 05, 2014 12:22
Yes, I send the bug report.
Maybe they ignore it because they are working in a new GUI system...
I hope that it will work right.
Exalia
Jan 28, 2014 12:16
This desperately needs attention in my opinion, not being able to switch MSAA on or off at run time without fatal effects is frustrating :(