Search Issue Tracker
Not Reproducible
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
Comments (1)
-
emmymaddy41
Oct 22, 2024 09:55
I fell for an online investment scam that almost messed my credit report up because I ran into debts, but thank God for HACKWEST AT WRITEME COM who didn't just help in recovering the money but also increased my credit score and fixed my report. I now have an excellent credit score and I strongly recommend Hack West for everyone in need of hacking services. Hack West is honest and reliable to his word.
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
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.