Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.6
Issue ID
BEHAVB-131
Regression
No
You have to click twice on the individual fields when setting Vector3 variables consecutively in Set Variable Value node
Steps to reproduce:
- Create and open an empty project
- Install com.unity.behavior
- Create and open a behavior graph (Assets > Create > Behavior > Behavior Graph)
- Right-click on an empty area and add a "Set Variable Value" node
- Create a blackboard Vector3 variable
- Assign the created Vector3 variable to the first variable of the Set Variable Value node
- Click on the X field on the node
- Type '1' and DON'T EXIT TYPING
- Click on the Y field on the node
Actual results: The Y field is not highlighted and you have to click it again to type in the value
Expected results: The Y field is highlighted and accepts inputs
Reproducible with versions: 1.0.6
Not reproducible with versions:
Can’t test with versions: 1.0.0 (in this version you can't type into the input fields on the node at all)
Tested on (OS): MacOS (M1) 15.1.1
Notes:
- This also applies to the inspector floating panel of the graph
- On the Blackboard floating panel, it works as expected (see video)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
After investigation, we’ve decided not to pursue a fix. The behavior stems from how the tool keeps the runtime asset strictly in sync with the authoring graph: when you set a field, the runtime asset is rebuilt immediately, which in turn triggers the authoring graph to reload. That reload interrupts the next field interaction, leading to the extra click.
Addressing this would require a significant architectural change to defer or batch updates, with non-trivial engineering and testing effort, and we don’t have capacity to take this on given the current priorities.
Resolution Note (1.0.X):
After investigation, we’ve decided not to pursue a fix. The behavior stems from how the tool keeps the runtime asset strictly in sync with the authoring graph: when you set a field, the runtime asset is rebuilt immediately, which in turn triggers the authoring graph to reload. That reload interrupts the next field interaction, leading to the extra click.
Addressing this would require a significant architectural change to defer or batch updates, with non-trivial engineering and testing effort, and we don’t have capacity to take this on given the current priorities.