State Tree variable binding context menu missing the "tasks" category

Development Programming & Scripting
, ,
1

I have a State Tree task that for one of its variables I’m trying to bind an output variable from another task. My problem is that when I open the binding context menu for the variable, the “tasks” category is missing.

[Image Removed]

Am I doing something wrong?

I have the same tasks on a State Tree in UE5.3 and there I can see the tasks category just fine.

[Image Removed]

Any help much appreciated!

2

Steps to Reproduce
In a StateTree create a state with 2 tasks: one task with an output variable, and a second task with an input variable matching the type of the first task’s output variable. Open the binding menu for the input variable on the second task - The tasks category is not shown. Thus, unable to bind the second task’s input variable to the first task’s output variable.

3

Hi Omer,

I have followed your repro steps and also crafted some tests of my own, but unfortunately I was not able to reproduce the behavior you described. In my tests, as shown in the screenshot below, the binding menu for an input variable correctly shows compatible input/output/parameter variables from earlier tasks (on parent states or on the same state and above on the task list). Just note that in UE 5.6 the “Tasks” category has been replaced with a separate category for each state to which the binding can be made (there were submenu entries on 5.3). I have tested both C++ and BP tasks.

[Image Removed]To help me try to understand what might be happening in your project, can you please provide some more details?

  • Are you running vanilla UE 5.6 from the launcher or building from source? In the latter case, are there any engine modifications that might possibly be influencing the behavior?
  • Are your tasks implemented in C++ or Blueprint? Are there any changes to the default properties of the affected variables (in their details panel on the BP case)?

It would also be very helpful if you could provide a very small repro project where the issue happens.

Best regards,

Vitor