[b16] Subgraph with keywords reports error

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

1 Like

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.

7586533--940555--Screenshot 2021-10-20 150434.png 7586533--940552--Screenshot 2021-10-20 150505.png

Raised a bug for this
FogBugz (unity3d.com)

1 Like

I can confirm that b15 also has this issue, didn't bother to download and try b14 but b13 does not have this issue.

Downloaded 2021.2.0f1, issue is not resolved and is not mentioned in the known issues section.

1 Like

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.

The issue has been fixed in package version 13.1.0 for 2022.1.0a13, a backport request for 12.x.x in 2021.2 is being evaluated: https://issuetracker.unity3d.com/product/unity/issues/guid/1374743/

1 Like

same issue, waiting for fix

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.

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.

completely agree

The fix has been backported to the 2021.2 branch a couple of days ago: https://github.com/Unity-Technologies/Graphics/pull/6425

It should become available in the Editor with the next vendoring update.



Thanks for the good news!

This is finally fixed in 2021.2.8f1

1 Like