Search Issue Tracker
Fixed in 12.0.0
Votes
0
Found in [Package]
10.2.2
Issue ID
1328761
Regression
Yes
[Shadergraph] Reordering and then renaming enum entries breaks existing enum nodes
Reproduces in 10.2.2
Doesn't reproduce in 7.3.1
Repro steps:
1. Create an Enum keyword on a shadergraph
2. Drag the keyword onto the graph
3. In the internal inspector, switch the first and last entries of the enum
4. Rename the first entry of the enum
Expected result: the first entry on the node is renamed
Actual result: the first entry on the node disappears
Note: the reorderable list for the keyword at this point contains two entries with the same ID
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment