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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
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).