After a change to how StateTree handles Sub-trees returning succeeded, StateTree can now get caught in a loop when trying to transition out of the StateTree. Sub-tree completion and status should trigger the linked state's transitions, but it is getting stuck in transitioning out of the sub-tree.
Expected Result: The tree exits after the delay is finished and no more debug text is displayed. Log indicates that tree has finished.
Actual Result: The tree gets stuck in a loop with the debug text still on screen and logs that repeat of the sub-tree completed and transitioning back into the sub-tree. Logs resemble this:
LogStateTree: Verbose: BP_STCube_C: Transition on state 'SubTreeState' -[(State Succeeded)]-> state '(State Succeeded)' LogStateTree: Verbose: BP_STCube_C: Completed subtree 'TestDebugLinked' from state 'SubTreeState' (TestDebugLinked): Succeeded
I am not able to find world outliner how to enable it?
How can i modify the param name in EQS node
How to achieve HLSL Multiple Render Target in Material blueprints?
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
What method is used to fill polygonal regions when drawing spline mesh at run time?
How does UMG set overlapping layouts?
Why is the ProceduralMeshComponent not drawing a face?
What property of the Slider is the image used when dragging?
How to properly terminate the DoWork thread function in FAsyncTask?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-187357 in the post.
1 |
Component | UE - AI - StateTree |
---|---|
Affects Versions | 5.2 |
Target Fix | 5.3, 5.4 |
Fix Commit | 25926193 |
---|
Created | May 30, 2023 |
---|---|
Resolved | Jun 19, 2023 |
Updated | Jun 19, 2023 |