Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Unity 2019.3.0f : #error "LODDitheringTransition" is not supported on GLES 2.0

Discussion in '2019.3 Beta' started by mikapote, Dec 12, 2019.

  1. mikapote

    mikapote

    Joined:
    Oct 24, 2018
    Posts:
    28
    Hi there. Since the first release candidate of 2019.3, I can't build my game on Android anymore. The following error is shown "#error "LODDitheringTransition" is not supported on GLES 2.0", for basic shaders like 'Universal Render Pipeline/Particles/Simple Lit or Universal Render Pipeline/Lit.

    Is GLES 2.0 really not supported anymore? Is it mentioned anywhere?
     
    Last edited: Dec 12, 2019
    mikapote, Dec 12, 2019
    #1

  2. phil_lira

    phil_lira

    Unity Technologies

    Joined:
    Dec 17, 2014
    Posts:
    584
    GLES2 is supported. LODDitheringTransition is not supported on GLES2 and I can't find where stock URP shaders use it. We are looking to repro this case here. Thanks for sharing.
     
    phil_lira, Dec 12, 2019
    #2
    mikapote likes this.

  3. Saicopate

    Saicopate

    Joined:
    Sep 25, 2017
    Posts:
    76
    Same here. After a few attempts it builds but there's no rule. Very annoying.
     
    Saicopate, Dec 13, 2019
    #3

  4. phil_lira

    phil_lira

    Unity Technologies

    Joined:
    Dec 17, 2014
    Posts:
    584
    We pinpointed the cause of this issue. A recent change in SRP shader library caused this. The only effect should be the error message. We have a fix in the pipeline now.

    Thanks for sharing this.
     
    phil_lira, Dec 13, 2019
    #4
    SamTyurenkov and mikapote like this.

  5. Driven

    Driven

    Joined:
    May 31, 2013
    Posts:
    77
    What is the solution for this besides waiting? 2019.3.f3 does not build due to this error and urp 7.1.6 is the latest version to pull from package manager.
     
    Driven, Dec 14, 2019
    #5

  6. SamTyurenkov

    SamTyurenkov

    Joined:
    May 12, 2018
    Posts:
    83
    It seems I have this issue as well. First attempt to build for Android right after Unity launch gives those errors:



    If you try to build again, right after those errors pop up - it works and a build is than produced, however the produced build renders only pink screen on Opengl ES 2 devices.

    I'm using 2020.1
     
    SamTyurenkov, Dec 15, 2019
    #6

  7. Driven

    Driven

    Joined:
    May 31, 2013
    Posts:
    77
    I tried rebuilding 5 times in a row, it doesn't help, restart neither, maybe it's luck with a 10% chance.
     
    Driven, Dec 15, 2019
    #7

  8. SamTyurenkov

    SamTyurenkov

    Joined:
    May 12, 2018
    Posts:
    83
    Quick workaround:

    I commented this void and errors dissappeared.

     
    SamTyurenkov, Dec 17, 2019
    #8

  9. Driven

    Driven

    Joined:
    May 31, 2013
    Posts:
    77
    Does this also fix the whole game being pink with gles 2.0?
     
    Driven, Dec 17, 2019
    #9

  10. SamTyurenkov

    SamTyurenkov

    Joined:
    May 12, 2018
    Posts:
    83
    Yes, In my case it did fix pink screen on gles 2.0 devices.
     
    SamTyurenkov, Dec 17, 2019
    #10

  11. Pixsaoul

    Pixsaoul

    Joined:
    Feb 10, 2014
    Posts:
    14
    I also had this error on the same version. For me it only prevents build I try in my CI with batchmode or on first try. a second build would work.

    I'll try with 2019.3.0f5 ;)
     
    Pixsaoul, Jan 19, 2020
    #11

  12. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,106
    This should be fixed in 7.1.7.
     
    LeonhardP, Jan 20, 2020
    #12

  13. _watcher_

    _watcher_

    Joined:
    Nov 7, 2014
    Posts:
    259
    Can confirm, updating Core RP Library to 7.1.7 fixed this error for me. Thanks!
     
    _watcher_, Jan 21, 2020
    #13
    LeonhardP likes this.

  14. LeifStro

    LeifStro

    Joined:
    Mar 23, 2015
    Posts:
    27
    Hey unity team, this same issue is now happening in Unity 2020.3.0f1, with Universal RP 10.4.0 + Core RP Library 10.4.0. I cannot build to Android without getting a bunch of these exact errors popping up.
     
    LeifStro, Mar 19, 2021
    #14
    zackblack likes this.

  15. zackblack

    zackblack

    Joined:
    May 17, 2015
    Posts:
    73
    I'm getting this now on 2019.4.23f1 and URP 7.5.3. Cannot built for Android. Help?
     
    zackblack, May 20, 2021
    #15

  16. hardartcore

    hardartcore

    Joined:
    Jan 27, 2017
    Posts:
    43
    @LeonhardP I can confirm that the issue still exist in URP 10.5.0 with Unity 2020.3.9f1 .
     
    hardartcore, May 25, 2021
    #16

  17. puppetisto

    puppetisto

    Joined:
    Jun 21, 2020
    Posts:
    14
    Hi all! I'm getting this error too on Unity version 2020.3.14f1 with 10.5.0 URP. Any help or fixes known? This is really maddening.
     
    puppetisto, Jul 31, 2021
    #17

  18. z3nbstrd

    z3nbstrd

    Joined:
    Jul 23, 2020
    Posts:
    3
    I'm getting this error in v2021.2.11f with URP v12.1.4. Specifically, with the Suntail_Foliage shader in the Suntail Village asset from the asset store
     
    z3nbstrd, Feb 19, 2022
    #18

  19. leuconoe

    leuconoe

    Joined:
    Oct 14, 2014
    Posts:
    15
    bump. same error in unity v2021.2.15, URP v12.1.5
     
    leuconoe, Mar 15, 2022
    #19

  20. gongchengshi

    gongchengshi

    Joined:
    Nov 9, 2016
    Posts:
    1
    same error in unity v2021.3.13, URP v12.1.7
     
    gongchengshi, Mar 8, 2023
    #20

  21. jjbcariaso

    jjbcariaso

    Joined:
    Oct 18, 2018
    Posts:
    3
    Bump. Same error in unity v2021.3.25f1, URP v12.1.11
     
    jjbcariaso, Jul 9, 2023
    #21

  22. Oliver2222

    Oliver2222

    Joined:
    Aug 17, 2022
    Posts:
    6
    same in 2022 I just had this error today is there a fix thanks
     
    Oliver2222, Jul 17, 2023
    #22