Search Issue Tracker
Fixed in 13.0.0
Fixed in 12.0.0
Votes
1
Found in [Package]
12.0.0
Issue ID
1354463
Regression
Yes
[ShaderGraph] Instances of SubGraph Nodes are not updated correctly when SubGraph's properties are reordered
How to reproduce:
1. Open a new URP project
2. Create a new Shader Graph and Sub Graph
3. Create two properties in the Blackboard of the Sub Graph
4. Drag the Sub Graph into the created Shader Graph
5. Re-order the properties in the Sub Graph window
6. Observe the properties of the Sub Graph Node in the Shader Graph window
Expected result: Properties are re-ordered
Actual result: Properties are not re-ordered
Reproducible with: 12.0.0 (2021.2.0b1, 2021.2.0b5, 2022.1.0a4)
Not reproducible with: 7.6.0 (2019.4.29f1), 10.6.0 (2020.3.13f1), 11.0.0 (2021.1.17f1), 12.0.0 (2021.2.0a21)
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
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
Resolution Note (fix version 13.0.0):
Fixed in 13.0.0 (2022.1.0a12)
ShaderGraph will ensure that the order of inputs on a subgraph node matches the order of the properties on the subgraph blackboard.
Resolution Note (fix version 12.0.0):
Fixed in 12.0.0 (2021.2.0b15)