Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.7.3
Issue ID
UVSB-1936
Regression
No
Visual Scripting Start State remains active when another Flow State is triggered
How to reproduce:
1. Open the attached project (VisualScriptingTestProject.zip)
2. Open scene Scenes/SampleScene
3. Press the Play button
4. Observe the Console
5. Click into the Game view and press Space
6. Observe the Console
Expected result: only one Flow State is actively updating (Start State is no longer active)
Actual result: both Flow States are actively updating
Reproducible with: 1.4.15 (2019.4.31f1, 2020.3.19f1), 1.6.1, 1.7.3 (2021.1.23f1, 2021.2.0b14, 2022.1.0a11)
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
- Shader Graph Importer's Documentation Reference button leads to a 404 page
- Crash on WriteParticleLineVertex when particle systems are rendered in a specific project
- Asset names longer than the allowed system file path are not handled gracefully
- Moving VFX Particles leave a ghosting trial in Ray Traced Screen Space Reflections
- A "Could not generate preview image" error is shown in the Console window when viewing a ".androidlib" asset
Resolution Note:
As it is possible to add multiple state flow in a same state graph, running in parallel, the Any State node need to be connected to the a sets of nodes that the user want to let escape at any states.