Search Issue Tracker
Fixed in 5.6.0f3
Votes
8
Found in
5.6.0f3
Issue ID
898863
Regression
Yes
AntiAliasing function does not work correctly, the rotated images still have the aliasing
Reproduction steps:
1. Open the attached project;
2. Open the scene "RotatedImage";
3. Observe an object "Image" edges;
Actual result: an image edges have hard aliasing (left side in the user image ).
Expected result: an image should not have so much clear aliasing (right side in the user image).
Reproduced with: 5.6.0f3, 2017.1.0b1
Not reproducible with: 5.4.5p1, 5.5.3f1
Regression introduced in 5.6.0a1
Comments (1)
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 ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
EwieElektro
May 01, 2017 08:37
I found out, when you activate MipMaps for UI Images/Sprites, it solves the problem. But it's not the best solution i quess. But it works...for me ;)