Starling

Starling_0.2 mesh tools. These components enable mesh parametrization, so it behaves like a surface - you can evaluate points at any place etc.

In 0.2 release, Starling enabled quasi-polyhedral mesh tools. These new components are organized in a new panel called "Alchemists" : 

How do they work ? You create polyline and each component converts it into polygonal mesh. Then it computes what it has to do. In the end component outputs polylines again, changed in some manner depending on components function.

DOWNLOAD from food4rhino.com

Why truncation and dual ? Because with these two operations you can make most of mesh operations as described HERE. I.e. ambo (rectify) is truncation with amount of 1.

Special thanks to : Michael Pryor for constant help&support and David Rutten for great advices.

 

It's highly recommended to use Starling with Weaverbird and [uto] MeshEdit.

 

More examples explaining new components soon.

Load Previous Comments
  • spiral

    great job, the prospect is in mesh optimization, is there any other examples with lots of cells equal to the "meshskin"?

  • Will Pearson

    Mateusz, I've been playing with the pmDecompose component as a method for creating Plankton meshes from polyline face representations. I've noticed some slightly odd behaviour and was wondering if it was intended. The problem, for me, stems from the fact that a closed polyline has its first vertex listed again at the end. These are not culled by pmDecompose, resulting in each face having one too many vertex indices.

  • Alimgarh Malik

    Hi Mateusz Zwierzycki,

    Please help me with this thing.

    An error occured during GHA assembly loading:
    Path: C:\Users\admin\AppData\Roaming\Grasshopper\Libraries\Starling_0.2.gha

    Exception System.NotSupportedException:
    Message: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.