Search Issue Tracker
Fixed
Fixed in 1.0.13
Votes
0
Found in [Package]
1.0.0
1.0.12
Issue ID
BEHAVB-347
Regression
No
OnStart root nodes execute in creation order instead of node position in graph
Steps to reproduce:
1. Create a new graph in Unity.
2. Add 3 OnStart (no repeat) nodes, each connected to a log message node that logs "1", "2", and "3" respectively.
3. Run the graph in the scene and observe the log output (should be "1, 2, 3").
4. Reorder the OnStart nodes in the graph visually, moving the 3rd OnStart node (logging "3") to the leftmost position.
5. Toggle twice an OnStart repeat to force graph rebuild (because there is another bug where visually reordering nodes doesn't rebuild the graph automatically - BEHAVB-344).
6. Run the graph again.
Actual results:
The logged output remains "1, 2, 3" regardless of the visual reordering of OnStart nodes in the graph.
Expected results:
The logged output should follow the visual ordering of OnStart nodes in the graph (in this case, "3, 1, 2" after reordering).
\\
Reproducible with versions: 1.0.0/1.0.12
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment