Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.2.X
Votes
0
Found in
6000.0.24f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-85189
Regression
Yes
An additional Add node is created when double-clicking on a node in the ShaderGraph "Create Node" menu
How to reproduce:
1. Create and open a new project using a URP template
2. In the Project tab, right-click and select “Create → Shader Graph → URP → Unlit Shader Graph”
3. Double-click on the newly created file to open the ShaderGraph window
4. Right-click anywhere in the ShaderGraph window
5. Select “Create Node”
6. Double-click to add any node (for example, “Math → Basic → Multiply”)
7. Observe the result
Expected result: Only the node that was selected in step 6 is created
Actual result: An “Add” node, in addition to the node selected in step 6 is created
Reproducible in: 6000.0.0b11, 6000.0.24f1
Not reproducible in: 2021.3.45f1, 2022.3.51f1, 6000.0.0b10
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Not reproduced by CQA
- An “Add” node is also created when double-clicking the window header to maximize the window
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
We could not reproduce this issue. It's possible that another change to our UX stack addressed this indirectly, or the repro conditions are more nuanced.
Resolution Note (6000.2.X):
We could not reproduce this issue. It's possible that another change to our UX stack addressed this indirectly, or the repro conditions are more nuanced.