Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.55f1
6000.1.15f1
6000.2.0f1
6000.3.0a4
6000.4.0a1
Issue ID
UUM-114073
Regression
No
Duplicating the Group Node in VFX Graph enters the renaming when the Group Node is selected slightly above its header
How to reproduce:
1. Create a new project and install the Visual Effects package
2. Create any VFX Graph and open it
3. Right-click in the VFX Graph tab -> Create Group Node
4. Right-click slightly above the Group Node text and select "Duplicate" or "Duplicate with edges"
5. Observe the results
Expected result: The Group Node is duplicated
Actual results: The Group Node is duplicated and the header of the original Group Node is in the renaming
Reproducible with: 6000.0.55f1, 6000.1.15f1, 6000.2.0f1, 6000.3.0a4
Reproducible on: macOS Sequoia 15.5 (M1)
Not reproducible on: No other environment tested
Note: The issue is not very easy to reproduce, for the best results, the Group Node should be selected by clicking above the text and right-clicked above the text
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.