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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment