I’m a bit busy ATM but I’ll try to create something for you that shows what I think would be interesting to make the plugin more versatile. Basically it’s about “directability” - having ways to tell the paths that they should follow a certain path or direction as long as possible.
This is an example from Houdinis “shortest path” with custom path costs:
You can see how the paths try to stay in the centre and only turn towards their individual endpoint when they “have to”.
Most natural forms are like that and it generates a much more interesting variety of patterns.
So I could imagine defining a spline curve as a “goal” or “attractor” that the shortest path tries to follow. Attractor behaviour would be good, so the paths don’t follow the guide too absolutely(or at least not if I don’t want them to).
Like you pointed out in the other thread, I’m not even sure if Shortest Walk is the performance hog or if GH simply has a hard time with lots of points no matter what tools you use. I worked with very detailed grids and the system became extremely slow.
Does the plugin use multithreading internally? In theory it should be possible to search each path in it’s own thread?
Cheeers and thanks again for your feedback!