Grasshopper

algorithmic modeling for Rhino

Hi hoppers,

can anybody explain why filleting a closed polyline at parameter t results in multiple closed curves, each with only one corner filleted?

Views: 4904

Attachments:

Replies to This Discussion

As an extension of my previous definition:

 

You could also use the basic fillet component in the previous definition I posted. This will allow you to remove a couple of other components.

That is really nice Vicente:) But after baking and measuring the fillet radius, there are some deviations from the set radius.
I'll add the definition(s) I used, and the polylines I checked them on. The first bit is a (silly) attempt that failed, but I thought I might as well just show it too.

Attachments:

Yes, I get that too.

What seems to be happening is that the fillet component reduces the radius automatically when the starting point exceeeds half the length of one of it sements.

I already use a similar cheap workaround in the definition so they acumulate and this means you can't use radii that is grater than 1/4 of the shortest segment's length.

 

The rhino command filletcorners doesen't have this limitation.

The fillet curve at a parameter component doesen't have this ilimiation either, so you can use that. Merge the end part of my previous definition with this one.

Thanks again Vicente, much appriciated!
Very creative use of language to write exceeeds :)
Nice one! (in the context of the word - the three e's, oh well I think you get it without me explaining).

I don't think the radius limit is too big a problem for most cases. I added a bit to make this also work if only one polyline is set. This was a nice challange, or is there room for improvement? Am I trying to scrape off milliseconds? ;)

Do you think we need to report a fillet bug? I didn't check if there are already any reports...

Thanks again Vicente, see you around.




Attachments:

It was actually an involuntary typo, but I see how it fits the context.

 

At first I thought it was a bug, but more probably it's an expected limitation of the way the fillet component is done. It seems that David's algorithm is not as good as the one in Rhino. Maybe you can ask him to write a better one.

A belated reply, but just wanted to say this definition works great.  I was working on something similar until I turned to the forum.  Great how you separated cases for single or multiple polylines.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service