Region Intersection never work - workaround

Dear all,

I'm pretty pissed off when components are supposed to work and they don't, especially when such components are pretty old fashion. (Trim will sometimes fail too)

I just found a work-around to share if your Region Intersection is not working for you.

I tried the component with very simple curves, a rectangle and a circle. And Basically it failed. I moved the curves slightly, and sometimes it will work. That is so frustrating. My dimensions are pretty large (1:1 in mm) which has coordinates going up to 100,000 units, dunno if this is the reason why it does not work.

So the work around here is to use the Trim with Region instead. Use two of them and have curve A trim by B and then reverse. Collect both Ci and Ci and join them.

Replies to This Discussion

Permalink Reply by kleerkoat on March 2, 2011 at 10:17am

nice, I'll work this into my definition that sometimes fails doing this.

Thank you!

Permalink Reply by Marcola on May 30, 2015 at 5:49pm

Great advice, Victor! I've been there many times and it is really frustrating and time consuming understanding why the "Region Intersection" component doesn't work sometimes.

Permalink Reply by David Rutten on May 30, 2015 at 11:48pm

What are your tolerances for that model? But in any case I'd like to have the geometry that fails so I can determine whether the bug is with GH or with Rhino, then file a bug report.

Permalink Reply by martyn hogg on May 31, 2015 at 3:31am

I often find my models fail and don't work or don't produce the results I am after and it is really frustrating... but then I realise I am the problem.

Is there a workaround for me?

Permalink Reply by David Rutten on May 31, 2015 at 7:06am

Yup, it's called Martyn 2.0*

* or 'procreation' to give it its proper biological term.

Permalink Reply by martyn hogg on May 31, 2015 at 8:06am

probably be 64bit and not work on my laptop tho :(

Permalink Reply by Sunghwan Yoon on June 4, 2015 at 10:09am