Shortest Walk error

Hi,

this error is rather common but I don't know what it means. It usually happens when there are a LOT of curves.

There is also a minor thing I don't understand about the sweep command. I input a single line as the cross-section, and a single curve (polyline) as the rail. And when the mitter is set to 1 (Trim) it creates 3 Brep. ???. When it's set to 2 (Rotate) it creates a single untrimmed surface, but the corners aren't filleted. Isn't it supposed to fillet the corners when it's set to 2?

Attachments:

shortest walk.gh, 12 KB

Replies to This Discussion

Permalink Reply by Thomas J. Mrokon on April 4, 2013 at 7:53am

I am using SW with more than 20K lines and it works.

Could you save your def without additional components?

Permalink Reply by Jesus Galvez on April 4, 2013 at 8:24am

I forgot to internalize the initial curve. This one has 143 initial lines and 90K after shattering them.

I can't seem to reproduce the sweep error, and didn't save the configuration.

Attachments:

shortest walk 2.gh, 12 KB

Permalink Reply by Jesus Galvez on April 4, 2013 at 9:02am

Ok I got it to work. Turns out I wasn't shattering the lines correctly. Though I don't know why shattering the lines incorrectly gives an "Index was outside the bounds of the array" error.

RSS