Search Unity

Bug New warning about texture parameter support in 2021.3.10

Discussion in 'Shaders' started by TJHeuvel-net, Sep 20, 2022.

  1. TJHeuvel-net

    TJHeuvel-net

    Joined:
    Jul 31, 2012
    Posts:
    838
    I just updated from 2021.3.9 to .10, and was greeted with these:



    A whole lot of shaders log this:
    WindowsPlayer "Tijmen-Lenovo" Shader 'Hidden/TerrainEngine/Details/Vertexlit' uses 153 texture parameters, more than the 64 supported by the current graphics device.

    I dont really understand whats going on, i highly doubt we are using 3000 textures in a single shader. Especially PostProcessing Uber which is the builtin PostFx v2. Using builtin pipeline.
     
    marcin-walus likes this.
  2. DevDunk

    DevDunk

    Joined:
    Feb 13, 2020
    Posts:
    5,043
    Tried deleting the library folder to reimport the project?
     
  3. TJHeuvel-net

    TJHeuvel-net

    Joined:
    Jul 31, 2012
    Posts:
    838
    The update from .9 to .10 was quite quick, back as well. It didnt reimport everything, nor do i really want it to.
     
  4. marcin-walus

    marcin-walus

    Joined:
    Feb 9, 2016
    Posts:
    10
    Hi. I have the same issue on iOS.
    It started in 2021.3.10 and it results in incorrectly displayed assets loaded from asset bundles.
     

    Attached Files:

  5. joshua_davis

    joshua_davis

    Unity Technologies

    Joined:
    Jan 5, 2021
    Posts:
    9
    Hi, can you file a bug on this with a repro project?
     
  6. Cherio4

    Cherio4

    Joined:
    Jan 4, 2020
    Posts:
    2
    I too have the same issue.
    I have updated Unity/HDRP from 2020.3.17 to 2022.1.16.
    The warnings occur when assets are loaded from asset bundles which were built with the older version Unity.
     
    Last edited: Sep 29, 2022
    LukeDawn likes this.
  7. JKort

    JKort

    Joined:
    Sep 14, 2017
    Posts:
    9
    I can confirm this. Additionally, assetbundles I built in 2021.3.8f1 seem to crash the application when I try to load them in 2021.3.11f1. Anyone else running into this as well?
     
  8. ringhino

    ringhino

    Joined:
    Aug 31, 2010
    Posts:
    39
    Same problem loading assetbundles created with Unity 2022.1.10 into Unity 2022.1.12 / 13 / 14 / 15 / 16 / 17 / 18 / 19 and 2022.2.0.b10

    Is a serious problem as many assets cannot be re-exported
     
  9. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    Please submit a bug report and mention the bug number in this thread. We'll ask QA to prioritise it.
     
  10. ringhino

    ringhino

    Joined:
    Aug 31, 2010
    Posts:
    39
    bug report submitted IN-19665

     
  11. Dominik-P

    Dominik-P

    Joined:
    Dec 22, 2013
    Posts:
    4
    Hello, Is there any update in this subject?
    assetbundles I built in 2021.3.8f1 seem to crash the application when I try to load them in 2021.3.11f1


    I have the same problem. Both old asset bundles and addressables are crashing iOS application
     
    tylearymf_unity likes this.
  12. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    Hello!
    I have just found the culprit. A fix is on its way - hopefully it will be there in 2-3 weeks in 2021.3.
     
    pdinklag, JKort and yhosoda like this.
  13. Dominik-P

    Dominik-P

    Joined:
    Dec 22, 2013
    Posts:
    4
    Last edited: Nov 7, 2022
  14. roka

    roka

    Joined:
    Sep 12, 2010
    Posts:
    598
    Happen also with WebGL using Unity 2021.3.13f. In the web browser console:

     
    Last edited: Nov 9, 2022
  15. jonkelling

    jonkelling

    Joined:
    Dec 18, 2019
    Posts:
    21
    I've been on 2022.1.10f1 for a while because of this bug as well. I'm pretty sure 2022.1.11f1 and up was when I started seeing it.
     
  16. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    Hi! A fix will be available in 2023.1.0a19; backports are in the queue.
     
  17. Qleenie

    Qleenie

    Joined:
    Jan 27, 2019
    Posts:
    868
    Hi, can you elaborate on "in the queue"? How long will it take? This is a pretty severe issue in a LTS, causing lots of trouble for users doing an update of a minor LTS version, which should be absolutely safe.
     
  18. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    "In the queue" means PRs are prepared and are going through the PR landing process. It usually takes around 2-3 weeks before a public version is available after the PR lands.

    If you rebuild your shaders/asset bundles (clear the Library/ShaderCache folder), the issue will go away.
     
  19. Qleenie

    Qleenie

    Joined:
    Jan 27, 2019
    Posts:
    868
    we have hundreds of asset bundles, created from Prefabs. Rebuilding would take quite some time. Also, deleting Library folder would not trigger a rebuild of those, I guess?
     
  20. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    Actually, you don't have to clear the shader cache, sorry for misinformation.
    You just need to rebuild the bundles.

    Alternatively, you can wait for the patch that has the fix.
     
  21. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    The fix will appear in 2021.3.15f1. I'll post here when the 2022 backports land as well.
     
  22. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    3,014
    The fix will also appear in 2022.1.24f1 and 2022.2.1f1.
     
    jonkelling likes this.