Grasshopper

algorithmic modeling for Rhino

Hi Everyone,

I'm looking for a way to simplify a mesh so that the amount of faces are sigificantly reduced.

At the moment ive got the frame of my "building" and I want to create a facade around it similar to the picture below (without the slats.) The mesh was crreated in grasshopper and I've tried a variety of things including Weaverbird ect. but nothing seems to give me the result I'm after!

https://storage.ning.com/topology/rest/1.0/file/get/2655030968?profile=original

Ideally im looking for 2/3 intersections of these planes within the space between the "framework". I've attached the rhino file so hopefully thats useful! I kmow this is quite similar to a previous discussion but I also ran though the steps guided in there to no success :(

Screenshots below:

Views: 10687

Attachments:

Replies to This Discussion

Kangaroo MeshMachine?

Try the attached (not panacea [and slow] ... but works in some occasions).

Attachments:

Hi Peter, that seems to be working! thanks :)

- Just a quick question - any idea how to distort the mesh further towards the centre of the brep? I cant find the "point attractor" version for a mesh!

Well... I have a variety of (the usual) freaky things (the black C# boxes you know) that do freaky things on meshes. In particular 2 sorts of defs come in mind for your case:

  • Get a planar region > mesh (or use MeshMachine for the input mesh) > distort randomly (using some direction vector). That one is very close on what you are trying to achieve: for each facade ... do this and that etc etc.
  • Get any mesh > distort (and/or reduce and/or omit faces) randomly (using mesh face normals and/or some predefined vector)  > freaky results.

I'll post something as soon as I can find it.

Thanks Peter,

Yeah the overall effect im after is to really pull all points of the mesh towards the centre in order to get a bit more variation in some of the not so interesting parts of the facade!

Thanks again :) H

Found something but I must remove some sensitive (internal) stuff AND deal with a "smallish" issue that I had plans to fix but never did it (I hate meshes AND Iceberg type of stuff AND random stuff AND computers).

The issue has to do with handling Mesh collections out of the Mesh.SplitDisjointPieces() Method. Meaning that depending on the cull Method (in order to "clean" a Delauney mesh and restrict it within a given region) ... you may get one mesh instead of a List of disjointed Meshes. It's a ultra boring matter of changing the Data Trees in a rather complex C# and other equally boring things.

See what it does (the Iceberg option ... makes "higher" random points the more they are further "inside" the region. There's a Vodka option as well that flips results (meshes or breps, solids or "sheets") randomly.

 

Thanks PETER!!!

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service