Unity Issue Tracker - Output Texture's RGB values are slightly different from the source PNG image when using Texture2D.LoadImage function

Duplicate

Votes

3

Found in

2017.4

2018.4

2019.2

2019.2.12f1

2019.3

2020.1

Issue ID

1199764

Regression

No

Output Texture's RGB values are slightly different from the source PNG image when using Texture2D.LoadImage function

Texture

-

Nov 20, 2019

How to reproduce:
1. Open the attached project's Scene labeled "Bug"
2. Enter the Play Mode
3. Exit the Play Mode after waiting for a few seconds
4. Open the "input.png" and "output.png" in the root Project's directory and Inspect the two images

Expected result: Image RGB values are the same
Actual result: RBG values of the "output.png" Image are different from the "input.png"

Reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.13f1, 2019.3.0b12, 2020.1.0a14

This is a duplicate of issue #1106629

Loading a PNG file with Resources.Load<Texture2D> and Texture2D.LoadImage produces different results

Log in to vote on this issue

Comments (1)

ANTONBORODA

Nov 20, 2019 14:06

Please also mind that this issue is not related only to EncodeToPNG(), the texture itself is broken during the Texture.LoadImage(), because even if you don’t write it back to disk and use it for real time display purposes, it’s still broken.

Search Issue Tracker

3