Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Resolved [b16] Subgraph with keywords reports error

Discussion in '2021.2 Beta' started by alloystorm, Oct 20, 2021.

  1. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    All shader graphs work fine in b13, after updating to b16, all subgraphs with keywords generate errors like this:

    Sub Graph has errors, asset ... at line 0
     
    burningmime likes this.
  2. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    I tested this on a new project and it is very easy to reproduce:

    1) Create new sub graph
    2) Add a new keyword to the sub graph
    3) Create a new shader graph
    4) Drag the sub graph to the shader graph and you will see the error.
     
  3. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
  4. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    Last edited by a moderator: Oct 21, 2021
    LeonhardP likes this.
  5. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    I can confirm that b15 also has this issue, didn't bother to download and try b14 but b13 does not have this issue.
     
  6. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    Downloaded 2021.2.0f1, issue is not resolved and is not mentioned in the known issues section.
     
    cheeze_12 likes this.
  7. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    Can someone confirm if this is indeed a bug or just an undocumented direction you are taking with Shader Graph?

    If there was a decision to not support keywords in sub graphs, please let us know.
     
  8. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,135
    alloystorm likes this.
  9. DrabanL

    DrabanL

    Joined:
    Nov 13, 2014
    Posts:
    41
    same issue, waiting for fix
     
  10. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    Thank you for the info.

    Can you also let us know when the backport request is approved and executed? Our project requires certain features only available from 2021.2 but we feel a bit uncertain to switch over to 2022.1 right now since it's still in alpha.
     
  11. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    Still not fixed in 2021.2.3f1, and it is not even mentioned in the known issue section. From severity point of view, this is no doubt one of the worst ones since it prevents all your shaders from working if you use keywords in subgraph and it is 100% reproducable. I don't see why this is not prioritized.

    I raised another bug report if that is what's required to get more attention.

    PS. I don't think it is reasonable to mark an issue as fixed when the fix is not available in the release stream that it is originally reported from. Please don't call an issue fixed when the "fix" is only available in an alpha.
     
  12. DrabanL

    DrabanL

    Joined:
    Nov 13, 2014
    Posts:
    41
    completely agree
     
  13. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,135
    Chrisi12er and DrabanL like this.
  14. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
  15. alloystorm

    alloystorm

    Joined:
    Jul 25, 2019
    Posts:
    88
    This is finally fixed in 2021.2.8f1
     
    LeonhardP likes this.