Hello, I’m trying to use NodeCanvas with FlowCanvas, Basically i have a behavour tree, starting with a sequencer with a bunch of nodes running flowscripts. for some reason im getting a huge slowdown doing this. Im using ‘On Update’ event for the first flow script and ‘On Enable’ event for the rest of the events. using ‘On Enable’ event for the first script will not allow it to run. (im using ‘On Enable’ because thats what i saw in your homepage pictures.)
So basically am i doing this correctly?
also Is the a way to nest flowscripts within flowscripts without the use of macros?
Do you mean that the OnEnable event node is not working for you, or something different? If so, can you please share a screen of the graphs?
You can’t have nested flowscripts within flowscripts, but using Macros is pretty much the same thing. Is there a reason you dont want to use Macros?
yes, the OnEnable will not work on the the first node but will work on the rest.
To be honest, i’ve no idea if i’m nesting flowscripts correctly, what event should i be using in the flowscript to be called directly from the behaviour tree? as using OnEnable or OnUpdate gives me huge slowdowns.
the reason i didn’t want to use macros was they are self contained and cant share the blackboard ad nested scripts do. (just my preference).
I just tested this out to confirm by creating a BehaviourTree with a Sequencer and a few nested flowscripts beneath it, similar to your example and it works as expected. The OnEnable event is called correctly in all nested flowscript nodes in order of execution, even in the first nested flowscript node as it should. :/
Using the OnEnable, OnUpdate and OnDisable are the correct events to use for nested flowscripts in a Behaviour Tree. What do you mean by slowdowns though? Do you mean performance wise?
Can you please send me the project to ‘support_AT_paradoxnotion.com’ so that I can check it out and see exactly what can potentially be going wrong here, cause I can’t find any bug, or reproduce the error you are facing in any way? The OnEnable is called correctly in all nodes here.