Search Issue Tracker
Fixed
Fixed in 1.0.7
Votes
0
Found in [Package]
1.0.6
Issue ID
BEHAVB-132
Regression
No
Parallel mode is set to Default when connecting to two nodes and choosing Run In Parallel Until Any Succeeds
*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 "Wait" node
# Duplicate the "Wait" node
# Connect the OnStart node to both Wait nodes (a pop-up window should appear)
# In the pop-up window, select "Run In Parallel Until Any Succeeds"
# Click on the Run In Parallel Until Any Succeeds node
# In the inspector, observe the value of Parallel Mode
*Actual results:* Parallel Mode is set to "Default"
*Expected results:* Parallel Mode is set to "Until Any Succeeds"
*Reproducible with versions:* 1.0.6
*Tested on (OS):* MacOS (M1) 15.1.1
*Notes:*
* This is also the case for "Run In Parallel Until Any Complete" and "Run In Parallel Until Any Fail"
* Focusing out of and back in the behavior graph window changes the node name from ""Run In Parallel Until Any Succeeds" to just "Run In Parallel", reflecting that it is in fact set to Default
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (fix version 1.0.7):
Adding a Run In Parallel node and its various types from the branch dialog will set the correct mode.