mesh+

Mesh+ is a set of user components which produce topological effects from mesh faces and point sets using variable methods of subdivision and normal based three dimensional distortion. 

We are pleased to announce the Beta Release of version 2.0

LINK TO FOOD4RHINO

Images tagged: Mesh(+)mesh(+)

The current version of mesh(+) is developed for:

 - Rhino 5 (32 & 64)

 - Grasshopper version 0.9.0056 (For Rhino 5)

 - Recommended Download: Weaverbird

  • Danila Babko-Malyi

    I am playing around with the face effects of Mesh (+) and am having a hard time understanding what to plug in into the inputs. In Weaverbird using multiple values on a component like thicken for distance allows you to manipulate every face separately as shown below. However in Mesh(+) the same procedure for a face effect results in creating a new mesh for each value. Is there any way in Mesh (+) to be able to manipulate the t value of a face effect for individual faces without them being unwelded.

  • David Mans

    Danila,

    Thanks for the suggestion, I have just posted an updated set of user components that integrate this suggestion for the Face Effects and Face Subdivision components. For face components you can now pass a corresponding list of variable per each mesh face or a single variable, and for Face Subdivide components you can pass variables which correspond to the shared vertex's. This distinction is needed to keep the new vertices aligned between adjacent faces. To clarify, input naming structure for variables is a follows.

    (m#)[mesh] = mesh inputs

    (c#)[boolean] = closed vs. open face 

    (s#)[boolean] = stellate vs. extrude along face normal

    (d#)[double] = distance values which correspond to rhino's model units

    (t#)[double] = unitized, (most often 0-1), variables which control face/ vertex based relationships

    (f#)[boolean] = (rare) flip between subdivision types

  • Danila Babko-Malyi

    David,
    This is great. Thank you for the update.

  • David Mans

    Danila,

    Thank you again for the suggestion.

    Tooltip descriptions have been added to all components.

    Will be adding new samples shortly.

  • David

    i can't download the example files,could you please upload the files again,many thanks!

  • David Mans

    David,

    The download for the samples seems to be working.

    Did you download them from:

    https://app.box.com/s/bhgfsnmwmfkzjuk5z13i

  • David

    something went wrong when i am download it,could you please attach it on you group page ,thankssss !

  • Wieland Schmidt

    Hi David,

    first of all thank you very much for mesh(+) its a great tool an I like it a lot.

    I tested the m(+) cross component and I was wondering if it is possible to get the same amount of mesh subdivisions on the upper and under flange? If I subdivide the mesh with WB like this I get an uneven appearance.

    Second question:

    Is it possible to build a component that creates a structure like this?

    Thank you and greetings from Munich, Wieland

  • David Mans

    Wieland,

    Taken a while to address this issue... I've updated the components... cleaned up a few other issues I came across in the newest upload DOWNLOAD HERE. Also added a new component with the structure you suggested in the second image.

  • David Mans

    David,

    Apologies for the delay in posting the sample files. Put together a more up to date set of samples. They are attached to this comment.mesh%28%2B%29-Samples.zip

  • Wieland Schmidt

    David, the new component works great, thank you very much. Wieland
  • ng5 Alex

    Hello!

    i am trying to input a list to the weave components and they dont accept lists. when i right click to select list access i get this error
    1. Specified cast is not valid. (line: 414)

    am i doing something wrong?

  • David Mans

    You are correct, the component's tool tip descriptions were incorrectly labeled. The components did not have list inputs as an options. However, I've updated this for the Weave, Link, and Net components, so that they can now have vertex based values. The Loop and Thatch components, still have only single value inputs.

    You can download the new component set from the usual link

    As a side note, because the components are all VB nodes, changing the inputs types without altering the actual scripts will always cause an error because they are used in the scripts specifically as either items, lists or trees.

  • ng5 Alex

    Hello again!

    this is great. thank you for the development of mesh+ and the update!

    may i wish for something? a mesh+ truncation would be very nice.

    i use the one that comes with starling but it would be nice to have it in mesh+ tab.

    if ngon meshes become available in rhino the possibilities with mesh+ are endless.

    cheers

    alex

  • Yutao Song

    Mesh+ is excellent, thanks!!

  • ALI ESLAMI

  • dvdrbls

    Hi David, fantastic tool, every time i use it i discover new things it can do, particularly i am attracted to the mesh mapping, the custom map example is great, but i don't understand completely because instead of just selecting a mesh to map, you put all the components to create one in the same definition as the mapping one, do you have an additional example of this?

    thanks!

  • David Mans

    I'll create some simple samples of the mapping component. I did find a mistake in the user objects where there are two copies of the face mapping component and the edge mapping is missing. I'll fix this and update the samples shortly.

  • Michael Pryor

    There seems to be a issue with Batwing where it cant accept 2 curves anymore (the issue seems to be the G1 input) If you use just G0 and then get height with "D" it works fine. I used it many times before and it worked with two closed curves. In this case is just two simple rectangles (one copied from the other)