Search Issue Tracker
Fixed in 12.1.0
Votes
0
Found in [Package]
12.0.0
Issue ID
1366383
Regression
Yes
Shader Sub Graph properties are displayed in a wrong order in Shader Graph Editor when Shader Sub Graph properties are reordered
Steps to reproduce:
1. Open the attached project "repro.zip"
2. Open Assets/subGraph.shadersubgraph
3. Reorder subGraph properties in the Shader Graph Editor window (drag '1' Float below '3' Float)
4. Open Assets/shaderGraph.shadergraph
5. Observe subGraph node in the Shader Graph Editor
Expected result: subGraph nodes properties are displayed in the same order as in Shader Sub Graph
Actual result: subGraph nodes properties are displayed in the incorrect order
Reproducible with: 12.0.0 (2021.2.0a4, 2021.2.0b15, 2022.1.0a1, 2022.1.0a10)
Not reproducible with: 7.7.1(2019.4.31f1), 10.7.0(2020.3.21f1), 11.0.0(2021.1.26f1, 2021.2.0a3), 12.1.0 (2021.2.0b16), 13.0.0 (2022.1.0a11, 2022.1.0a12)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 12.1.0):
Fixed in Shader Graph 12.1.0 available for 2021.2.0b16 and up