MeshMachine update

A minor update to the remeshing component (read about the earlier release here)

This adds the option to also scale the triangle size by distance from the boundaries:

download this new version here:

(replaces the previous version, no need to change any of the other files)

The 2 new inputs are BoundaryScale and BoundaryDistance

If BoundaryScale is set to 1 (the default) then it has no effect and everything else works as before.

If it is set to (for example) 0.2, then the mesh edges along the boundaries will have a target length of 0.2 multiplied by the Length input value.

The BoundaryDistance input controls the size of the transition zone from this reduced boundary edge length to the standard edge length. For example, in the image below, on the left the BoundaryDistance is 4.0, and on the right 10.0

and here's an example of a circle packing with boundary gradient (generated by using the CPMesh component from Kangaroo on the output of MeshMachine):

Comment

You need to be a member of Grasshopper to add comments!

Comment by Duncan W on June 17, 2014 at 12:23am: Further question: Is it possible to somehow set a minimum edge length when using mesh machine?

When I approximate a wavy freeform surface with triangles, I need the CurvatureAdaptivity to work but not go lower than a particular minimum edge length. Even if this means a loss of curvature information. I am unsure how to incorporate this into my definition.

Comment by Daniel Piker on June 16, 2014 at 11:51am: Duncan - ah yes, forgot to mention - I included a legacy component so that previous definitions will still open, but when dragging a new meshmachine component from the toolbar it will always be the new one

Comment by Duncan W on June 16, 2014 at 5:13am: Fixed it. I didn't realise both the old and new component could co-exist. When I load the old example files, it's showing the old MeshMachine. But when I select a new one from the toolbar, it's the new one.

Comment by Duncan W on June 16, 2014 at 2:28am: Thanks for the swift response. I had restarted Rhino, yea.

Searched for *.gha mesh using Win7 search and deleted the instance I indeed found in users/downloads. It's still loading the old component in GH though. I double-checked the GHA in Libraries folder, but it's the 30kb one so should be correct?

Any other ideas?

Comment by Daniel Piker on June 16, 2014 at 1:58am: Duncan - it sounds like it is still loading the old component from somewhere on your computer. Have you restarted Rhino? Also try deleting the old GHA from the downloads folder.

Comment by Duncan W on June 16, 2014 at 1:44am: Looking so exciting. I've replaced the new GHA and saw it's a few KB larger. Yet in GH it's not showing the two new inputs you mentioned, and as I see them in NikFromNYC's screenshot.

Any idea what could be wrong?

Comment by Mathias Gmachl on June 11, 2014 at 5:18am: Beautiful idea running CP Mesh as a second stage.

Comment by Khaled ElAshry on June 11, 2014 at 5:03am: Nice work, I will definitely be using it

Comment by ntoniceddu on June 11, 2014 at 4:15am: this is great daniel thanks! i was trying to do this via script waiting for this feature in mesh machine, what i have done was to use divided points on the boundary courve and then using them as attractors.. but the result was not good as your, obviously, you genius!