Offsets fail seemingly randomly

See attachment. All of the tiles are offset by -0.01. For some the offset produces garbage, although they are large enough. What could be the issue?

What I want to achieve in the end: Give all tiles a negative offset. Those that are too small should disappear entirely.

I'm running Grasshopper with the latest WIP. The failed offsets also happen with Grasshopper in Rhino 5.

Attachments:

screenshot.png, 297 KB
draft.gh, 7 KB
version.png, 118 KB

Replies to This Discussion

Permalink Reply by David Rutten on February 12, 2017 at 6:49am

Unfortunately the Rhino offset function was never designed for this sort of use, it was assumed that there would always be a user to intelligently pick a location on the offset which made sense. Since it's part of Rhino core it is out of my hands (both my own attempts at writing a better offsetter have failed miserably), but you can probably get the Clipper plugin (polylines only, but it works really well) to help you out right now.

Permalink Reply by Felix E. Klee on February 12, 2017 at 7:47am

Thanks! This indeed does the trick for the little example.

Issues that I need to sort out:

As PolyOffset offsets in both directions, there is an unwanted frame around the entire set of polygons. I could remove that by hand after baking.
I don't know how to install the plugin into WIP, but with version 5 it works fine.

Attachments: