Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
5.5.0f3
Issue ID
859222
Regression
No
Black edge on Sprites imported with Alpha Source = From Gray Scale
BY DESIGN:
GrayScale to Alpha conversion is as follows :
T gray = (red + blue + green) / 3;
During conversion R G B values are left intact. Only Alpha value is changed. Hence RGB values of gray areas remain the same and gray shades in final sprite too.
Importing a sprite texture with "Alpha from Gray Scale" set to true leaves a dark edge around the imported sprites.
Steps to reproduce:
1. Create a New project
2. Import "Test.psd"
3. Set Texture Type to Sprite (2D and UI) and Alpha Source to From Gray Scale
4. Click Apply
Result: a black edge around the sprite appears.
Reproduced with: 2017.1.0b4, 5.6.1p1, 5.5.3p3.
Not reproduced: 5.4.5f1 (no Alpha from Gray Scale function in this version).
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This has been added as a feature request in the team backlog. Closing this bug report and will track as feature request going forward.