Blackboard variables not showing in "Run Subgraph" node inspector

I had my subgraphs with a blackboard to share some commom fields that was working in 1.0.3.
After the update the blackboard fields are not showing anymore when I click on the “Run Subgraph” node. It some works for variables that ware already set, but right now I cannot change or set new ones.

Am I doing something wrong?


Thanks for the report, will bring it to the team.

Hi @jorgezer0,

This is actually a change we intended, there was an issue with using blackboard variable references & it’s default values which made us make this decision.

Would you be able to setup a blackboard variable & reference the blackboard asset in this variable directly inside the subgraph to achieve the same result / functionality you need?

Is passing the blackboard down from another graph needed for your specific case? Do you think you would like to also have this functionality in the future?

1 Like

So we should not use shared blackboards anymore? We should only use the subgraph internal variables and reference use their fields in the “RunSubgraph” node inspector?

I had a bunch of variables that I wanted to use by some other subgraphs, so now I will have to recreate the same vairable a lot of times and “reconect” them among my sub graphs.

Hi jorgezer0,

Sorry for the confusion that this change is causing. This is an area we are actively refining the design around and we would actually appreciate your input on the matter.

When designing such UX, we try to think about what problem we are trying to solve while trying to implement a solution that would still promote good practise. For instance, the previous change has been made backed by the following idea:

  1. Use RunSubgraph Static when you want to modularize and reuse graph behavior as functions where the logic stays the same - so the parameter should also be the same.
  2. Use RunSubgraph Dynamic when the logic can change and the parameters can follow an interface.

These were not the only motivation behind the change, we also had inherent issue we could not solve at the time.

But you are raising a good point:

Could you provide us with some details about the graph story you were trying to make using the RunSubgraph node? This would help us better understand use cases.

Thank you!