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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment