Optimization with a Kangaroo2 solver

Hi @natalia.stephanou

I’m afraid I don’t understand. Unlike the main Kangaroo solver, the Zombie solver component should work like any other standard Grasshopper component - if the input changes, the output will not update until the component has finished solving.
Try with any other GH component that takes a few seconds to calculate (say a Voronoi3d with 1000 points), change the input and you’ll see the output stays as the previous value while the component calculates, then changes to the new value, without ever outputting null in between.

So I think the issue might be coming from the way Octopus handles solution updates. I see what sounds like a similar issue happening here even without Kangaroo:

@robert_vier - can you shed any light on this?