David, Thanks for the reply. The section curves will be closed and proper if I use the intersection or section commands to the same baked geometry. It seems to miss occasionally small strips of surface that are a part of the polysurface. Thanks again and I'll look for the new release.
Best, ga On Feb 16, 4:41 am, David Rutten <[email protected]> wrote: > Hi ga, > > Grasshopper merely calls Rhino functions for all intersections/ > booleans. If it's busted in Grasshopper, it's busted in Rhino. > Many Rhino functions output single surfaces (Loft, Sweep etc.), but > when you run these commands in Rhino, you sometimes get polysurfaces. > This was a mistake on my end; I forgot to 'fix' the surfaces if they > had sharp creases. The new version of Grasshopper will output > polysurfaces for all these components. > > If you bake the shapes that go into the section component and perform > an _Intersect in Rhino manually, do you get proper, closed sections? > > -- > David Rutten > [email protected] > Robert McNeel & Associates > > On Feb 16, 2:56 am, ga <[email protected]> wrote: > > > Is anyone getting similar error in using the Section Node between a > > BRep and a Plane? Following thread and image links below. The image is > > from a simple tower exercise using a driver diagram in GH x4 to loft > > into a tower. Then using regular interval sectioning, some sections > > are incomplete and therefore not closed causing them to be skipped > > downstream when using the planar surface node. The loft is understood > > by GH as a "Untrimmed Surface." When baked, which is the surface to > > the right, it is a polysurface and intersection or section commands > > return closed curves. Any hints on why it is incomplete at some > > intersections and not others? Could it be in the intersection > > algorithm in GH? > > >http://groups.google.com/group/grasshopper3d/browse_thread/thread/458... > > >http://grasshopper3d.googlegroups.com/web/20090215_sectionError.jpg?g...
