Grasshopper

algorithmic modeling for Rhino

Hi,

I'm wondering why GH makes a single surface out of this sweep based on a polyline with filleted corners.

I prefer having splits at tangents like what Rhino's sweep does, in this particular case at least.

<UPDATE>

I figured that the "Pipe" component was a better choice for me here since, well... I want to model pipes.

This time, the result is a polysurface made up of cylindrical an toroïdal surfaces.

Views: 356

Attachments:

Replies to This Discussion

It probably wasn't as conscious a decision as I'm about to claim, but I suppose it makes more sense to have a single surface whenever possible as that provides a single UV domain for the entire shape, whereas a polysurface would consist of multiple faces, each with their own domain. Sampling a polysurface, extracting spanning isocurves, extracting subsurfaces, etc. etc. are all significantly easier when the target shape is a single surface.

It's true that a surface with multiple internal knots can cause problems with certain Rhino operations (and especially meshing), it's always easy to turn a surface with creases into a polysurface, but the other way around is a lot harder.

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2025   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service