Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.12
Issue ID
BEHAVB-361
Regression
No
Behavior execution order isn't right when behavior start another behavior in parallel
Steps to reproduce:
1. Open the attached project: IN-117201
2. Open the “SampleScene” (Project Window → Scenes → “SampleScene“)
3. Enter Play mode
4. Observe the messages in the console
Expected result: The console should show these results
Spawner: Spawn [101]
Spawned: First Node [101]
Spawned: Second Node [101]
Spawned: Third Node [101]
Spawner: Branch End [101]
Actual result: The results that the console actually shows
Spawner: Spawn [101]
Spawner: Branch End [101]
Spawned: First Node [101]
Spawned: Second Node [102]
Spawned: Third Node [102]
Reproducible with: 1.0.0(6000.0.60f1), 1.0.12(6000.0.60f1, 6000.2.8f1, 6000.3.0b7, 6000.4.0a3)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
This ticket was opened by accident.