Search Issue Tracker
Fixed in 5.6.0f3
Votes
0
Found in
5.5.0b10
Issue ID
849356
Regression
No
TextureImporter removes the white Alpha channel
Steps to reproduce:
1. Open the attached project (Unity5_BugReport_TextureImporter_RemovesAlphaChannel.zip)
2 Select Assets/Texture.tga (with completely white alpha channel)
3. Observe: Texture has no alpha channel in Unity (but actually it has)
Expected result: If a texture provides an alpha channel and the import setting "Alpha Source = Input Texture Alpha" is set, TextureImporter should use the alpha channel of the texture regardless of its content
Actual result: TextureImporter discards that alpha channel
Reproduced with: 5.3.6p4, 5.4.2p3, 5.5.0b10, 5.5.0b11
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
ElicaIWD
Nov 21, 2018 12:56
Still present in 2017.3.0f3 & 2018.2.5f1.
I don't actually "mind" this behaviour, but I would like to know if I can rely on it or not. We need to automatically detect if there is any relative information in the alpha channel, so if Unity does for us, it's a plus, as long as it is not a "bug" that is likely to get fixed in a future version.