@Gavalakis
I debugged the code of the parallel node, it seems that you are not clearing the finishedConnections variable which causes you to count the same connection twice on two different runs of OnExecute
As you can see in the attached image right after the loop that counts the finished connections you have 2 connections marked as finished, but when inspecting the outConnections you can clearly see that one of them is still with status=running
So, this node thinks both of it’s children are done (you can also see in the gif that that is not the case) and then calls
ResetRunning in the check for finishedConnectionsCount == outConnections.Count
For what ever reason, either the node starts off with one connection counted as finished, or there is another bug with clearing the the finished connections, in either case you can see the frustrating result in the gif above.
Attachments:
image_2024-02-15_003153335.png
image_2024-02-15_003438826.png
Login
Register
By registering on this website you agree to our Privacy Policy.