Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.13
Issue ID
BEHAVB-369
Regression
No
[UX] Deleting or renaming “Edit Subgraph Representation” should not be presented as an option
Steps to reproduce:
1. Create new Unity project
2. Open Package Manager window
3. Install Behaviour package (com.unity.behavior)
4. In Project window create Behaviour Graph (Create > Behaviour > Behaviour Graph)
5. Open Behaviour Graph
6. In Behaviour Graph > Inspector, press on “Edit Subgraph Representation” button
7. In empty field type “testing”
8. Change Variable from “Regular Text” to “GameObject”
9. Press “Confirm”
10. Back in Blackboard right-click on “Testing” GO Variable and select “Delete” from context menu
11. Observe the Variable
Actual results: The variable gets recreated and it is not clear to the user why
Expected results: The option to delete and rename subgraph variables are grayed out and there is a clear distinction between a subgraph variable and other variables.
Reproducible with versions: 1.0.13 (6000.0.62f1, 6000.2.10f1, 6000.3.0b9, 6000.4.0a4)
Tested on (OS): Ubuntu 22.04, macOS Silicon, Tahoe 26.0 (M1)
Notes:
- the same applies to renaming
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
we don't foresee this issue being fixed, and since it is technically by design, the impact of fixing this won't be worth the effort.
Resolution Note (1.0.X):
we don't foresee this issue being fixed, and since it is technically by design, the impact of fixing this won't be worth the effort.