Search Issue Tracker
By Design
By Design in 1.0.X
Votes
0
Found in [Package]
1.0.12
Issue ID
BEHAVB-349
Regression
No
Behavior Graph subgraphs are not showing completion when debugging
How to reproduce:
1. Open the attached “IN-118082.zip” project
2. Open the “SampleScene” scene
3. Open the “Main.asset” Behavior Authoring Graph in “Assets/Behaviours” directory
4. Press Debug
5. Select “Cube”
6. Enter Play Mode
7. Observe the BehaviorGraph
Expected result: Subgraphs show success upon completing
Actual result: Subgraphs are stuck on running or waiting
Reproducible with: 1.0.9 (6000.0.59f1), 1.0.12 (6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1)
Not reproducible with: 1.0.8 (6000.0.59f1)
Reproducible on: Windows 11 Pro (24H2)
Not reproducible on: No other environments tested
Note: Bug is only visual and the subgraphs are actually completing, Debug is not showing proper completion
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
- 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
Resolution Note:
if you add a wait node after the run subgraph node, you will see that the run subgraph node indeed displays a debug checkmark indicating success
Resolution Note (1.0.X):
if you add a wait node after the run subgraph node, you will see that the run subgraph node indeed displays a debug checkmark indicating success