Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0b6
6000.6.0a3
Issue ID
UUM-140728
Regression
No
Graph Toolkit Connections don't break when Data Mode is changed
Steps to reproduce:
- Open the "GTKETs.zip" project
- Open the "New Graph" asset in Graph editor
- Expand the "Actor Name" variable in the Blackboard
- Change Mode to "Single"
- Observe the grid in the Graph editor
Actual results: The wire doesn't break
Expected results: The wire between the variable and the node break
Reproducible with versions: 6000.5.0b6, 6000.6.0a3
Can’t test with versions: 0.4.0-exp.2 (6000.3.0a6), 6000.4.5f1 (Lists are not displayed)
Tested on (OS): Windows 11 Pro (25H2)
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
- "Interruption Source", "Ordered Interruption" and "Can Transition To Self" fields are not pasted to transition settings when pasting transition parameters
- “TerrainLit” is available as a Material option in UI Shader Graph's Graph Settings, and selecting it causes shader compilation errors in the Console
- HDR Gradient Editor color label and gradient display incorrect color after selecting Editor window color with color picker
- "Install 2D Sprite Package" button in Sprite Renderer is disabled when no Sprite is assigned, contradicting its own help text
- Users are prompted 2 times if they want to discard the Shader Graph when closing Shader Graph Window when the Asset has already been deleted
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.