Search Issue Tracker
In Progress
In Progress in 1.0.X
Votes
1
Found in [Package]
1.0.2
Issue ID
BEHAVB-1
Regression
No
Subsequent runs of subgraph leads to different output using WaitForAll node
*Description*
*Initial Setup*
Create the following graph:
# *Start* (Repeat On)
# *Run In Parallel*
## *Log* 1
## *Log* 2; *Wait* for 3 seconds
## *Log* 3
# *Wait for All* (1, 2 and 3 above)
# *Log* 4
*Steps to reproduce:*
Put the graph in a scene and run
*Actual results:*
# First Run
{code}
1
2
3
4 // after 3 sec
{code}
# Second Run
{code}
1
2
3
4
4
4 // after 3sec
{code}
*Expected results:*
Every run should have the same output:
{code}
1
2
3
4 // after 3 sec
{code}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment