Search Issue Tracker
Duplicate
Duplicate in 6000.5.X
Votes
0
Found in
6000.4.0b7
6000.5.0a6
Issue ID
UUM-133457
Regression
No
Graph Toolkit's Variable becomes unfocused when its Flow Direction is changed and a Node was added to the Canvas
How to reproduce:
1. Create a new Unity project and import the "Graph" Script and "Test" Graph
2. Open the "Test" Graph
3. In the Blackboard, select the "New Variable"
4. In the Graph Inspector, change the "Flow Direction" and observe the results
Expected results: The Variable doesn't become unfocused
Actual results: The Variable becomes unfocused
Reproducible with: 6000.4.0b7, 6000.5.0a6
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: Reproducible only if the Placemat wasn't unfocused after creation
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
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!