I’m having a strange situation. I had a behaviour tree and everything was working great. But I needed to add some additional logic to it.
Once everything was added I noticed that the service on one of my components isn’t running any more. I breakpointed the behaviour tree and the service that is supposed to run, but it’s just not happening.
If I remove the first two selectors. (exec path: 0 - 1 - 2) and connect my root directly to the service, works fine. The jobtype blackboard condition passes so it should start running my service, right?
Did you ever resolve this issue - I am having similar problems with my service not running except very rarely - even though the execution loop is clearly passing through the selector node it’s tied to.
I think I may understand whats going on, I ran into a similar problem but I believe the issue was to do with the Blackboard Based Condition decorator asking for a value that hasn’t been set because the Service hasn’t actually run yet.
E.G.
The service runs on a tick which isn’t happening until it gets into your sequence, you never get into the sequence because the blackboard based condition never recieves a value because its waiting on the service to give it one. They end up stuck waiting for eachother to make a move. A quick hacky way I solved this was adding a value in the selector to the right that just told the BT to wait 0.0s so that the service had a chance to give the blackboard based condition a value to check
