Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
Issue ID
UUM-121701
Regression
No
Visual Effect Graph error message does not disappear and lasts forever until the Visual Effect Graph is reopened even when the error causing connection/node is deleted and Visual Effect Graph is saved
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Install the Visual Effect Graph package
- Create a new Simple Loop Visual Effect Graph (Assets > Create > Visual Effects > Visual Effect Graph)
- Open the newly created Simple Loop Visual Effect Graph
- Create a new "Random Selector Weighted" node
- Connect the "Random Selector Weighted" node's output to the Drag Coefficient
- Observe the Visual Effect Graph
- Delete the "Random Selector Weighted" node and its connection
- Save the Visual Effect Graph
- Repeat step 7
Actual results: The “An edge with the same input and output already exists” error does not disappear and remains forever until the Visual Effect Graph is reopened
Expected results: The “An edge with the same input and output already exists” error disappears
Reproducible with versions: 6000.0.60f1, 6000.2.8f1, 6000.3.0b6,
Can’t test with versions: 6000.4.0a2 (no error messages appear due to UUM-121702)
Tested on (OS): MacOS Silicon Sequoia 15.6.1
Notes:
- The error message still remains even after deleting the connection or the "Random Selector Weighted" node and saving the Visual Effect Graph
- Closing the Visual Effect Graph and reopening it seems to be the only way to get rid of the error message
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-120233