Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.6.2f1
Issue ID
948130
Regression
No
PSD containing pixels of varying transparency but none fully transparent, displays alpha incorrectly
Warning: this was not reproduced on 2018.1.0a1, but I wanted to let the development team know about it in case it's something important
Steps to reproduce:
1. Open any Unity project
2. Import both of the attached PSD files
Actual result: The area of Error.psd that has the same transparency as the black and white areas of Working.psd looks different (with or without Alpha Is Transparency enabled), see atttached image sample.png
Expected result: no difference between the files
Note: the Working.psd file has one difference - it contains a vertical band of fully transparent pixels near the middle. Making some pixels fully transparent in the Error.psd makes it import correctly (see transparencyexample.png).
Note 2: comparing the results in Unity and Photoshop it's more likely that the Error.psd is imported as a more accurate representation in regards to the actual alpha channel within the file, however, the behavior is still inconsistent.
Reproducible with: 5.6.0f3, 5.6.2f1, 2017.1.0f3, 2017.2.0b11
Not reproducible with: 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment