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
- [Vulkan] Crash on with multiple stack traces when rendering large Terrain with specific hardware
- Crash on SkinnedMeshRendererManager when interacting with a prefab generated with uncombined meshes using Synty Sidekick Character Creator
- Crash on folly::detail::safe_assert_terminate_v when updating the Meta XR SDK Packages
- The text font falls back on a different font depending on the fallback font used
- Template is opened in Isolation when opening it in Context and users Save the UI Document when prompted to do so in UI Builder
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.