Search Issue Tracker
Fixed
Votes
1
Found in
2018.4
2019.4.4f1
2021.1
Issue ID
1276004
Regression
No
PNG Texture has lower quality when loaded during Runtime
How to reproduce:
1. Open the attached project's "case_1276004-Project.zip" Scene labeled "SampleScene"
2. Enter the Play Mode
3. Observe the Texture on "EditorVersion" GameObject
4. Observe the Texture on "LoadedVersion" GameObject
Expected result: Textures should look the same
Actual result: Texture loaded during Runtime is of lower quality
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.9f1, 2020.2.0b7, 2021.1.0a1
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:
Both the imported and the runtime texture are identical when using equal importing setup.
The main difference was that "Alpha is transparency" is enabled on the version inside the texture importer.
This causes some pixels (with alpha == 0 ) to be different due to alpha dilation.
When disabling this option, I verified that the pixels of both textures are binary identical (on the GPU).
Artifacts present in bug repro case seem to be the result of the specific rendering setup (rather than a bug).