Weird/Wrong Sweep2 behavior?

Replies to This Discussion

Permalink Reply by Riccardo Majewski on January 7, 2015 at 3:40am

Curve seams of the rails. Check them and you will probably understand everything by your own...

Your rails are polylines! Each composed by 4 curves.

The problem is that the start point of the 2 rails is set (by rhino default) a the start of the first curve composing the polyline (the rail), and NOT where you placed the section.

Usually in rhino this problem does not exists... but hey, we are in grasshopper now..

You can solve this with 3 methods:

1- Adjust the seam point of the 2 rails in rhino, moving them to where your section is. So you can "feed" grasshopper with ready food. (but, if you'll explode and rejoin the curves of the rails you'll probably re encounter this problem, other than having to relink the curves to grasshopper) 

2- Move and align the section to where the rails's seams(startpoints) are. (this is a stupid method though)

3- (see attached file) In Grasshopper, get the Endpoints of the sections, use those 2 points with "curve closest point" component to get the parameter on the rail, and the adjust the seams on the rails using those parameters.

P.S. Section's Endpoints are 2 , the rails are 2... to "combine" the correct Endpoint with the correct rail, you can add a sorting method listing the "curve closest point" nearest to the Endpoint for both cases;

in my definition you can see the order is inverted...

Or you can simply check and combine manually correct endpoint to each rails...

Tell if you still have problem.

bye!

Maje

Attachments:

• WeirdSweep2_fixed.gh, 12 KB

Permalink Reply by Florian Bendl on January 7, 2015 at 11:39am

Hi Riccardo,

thanks a lot! Was unaware till now of seam adjustment...never stopping to learn new things here! Works like a charm.

Thanks,

Florian

Permalink Reply by Shong on June 12, 2016 at 9:28pm

Hey Riccardo Majewski,

Thank you very much!

Learn a lot from your definition!