Search Unity

  1. We would like to hear your feedback about Unity and our products. Click here for more information.
    Dismiss Notice

"Normal Quality" image compression looks bad!!!

Discussion in '2019.1 Beta' started by trappist-1, Mar 2, 2019.

  1. trappist-1

    trappist-1

    Joined:
    Mar 26, 2017
    Posts:
    453
    I just compared identical images in 2018 and 2019 editors, and quite frankly the 2019 looks really bad.

    This is what I see in 2019 (notice the rainbow effect):

    By changing the setting from "Normal Quality" to "Low Quality" also doesn't change. So maybe the "normal compression" mode was removed?

    In both editors I had compression set to "Normal Quality" and only 2018 looked smooth and without crazy rainbow colors.

    Do I have to change every single image in my project to "high quality" so they look like 2018 did?

    Here's the original image:


    Why are the default images so bad now?
     
    Last edited: Mar 2, 2019
  2. AcidArrow

    AcidArrow

    Joined:
    May 20, 2010
    Posts:
    5,618
    How does normal look in 2018?
     
  3. trappist-1

    trappist-1

    Joined:
    Mar 26, 2017
    Posts:
    453
    Rainbow effect only slightly apparent, but I never noticed it. It was nothing like what I'm seeing in 2019.
     
  4. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,601
    I believe it's a regression. I submitted a bug-report for the issue:
    (Case 1132906) 2019.1: Color banding with "Normal Quality" texture compression
     
    LeonhardP and trappist-1 like this.
  5. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,601
    AntiSilence, trappist-1 and AcidArrow like this.
  6. Peter77

    Peter77

    Joined:
    Jun 12, 2013
    Posts:
    3,601
    Just a heads up, it should be fixed in 2019.3.0a2, according to the changelog:
    https://unity3d.com/unity/alpha/2019.3.0a2
     
    LeonhardP, trappist-1 and AcidArrow like this.
  7. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    1,411
    It will also be fixed in 2019.2.0b3. The 2019.1 backport is still pending.
     
    trappist-1 and Peter77 like this.