the distance between the points so the triangles it creates don't have very long sides.All my attempts were very far from the goal so I'm only uploading the population. Pictures 2 and 3 demonstrate how the software works and changes which dots to connect. The software can be found here: https://www.behance.net/gallery/10543937/Image-Triangulator-AppThank you very much!…
d fly with a Porsche flat six).
2. Added a double (nested) Anemone thing (and the Mateusz version) and some comments.
3. Added a stupid "arm maker" cluster ... primitive/ugly/pointless - see one prototype attached about how to do it (you'll need a top feature driven CAD app for this - notice the Teflon low friction ring).
4. In order to "adapt" the cluster arm you need some "stretch" capability (orient, scale et all are the 1st step). Of course putting the cluster into the 2*loop is the art of pointless (Mateusz misinterpreted my bitter comments as regards the "slow" thing, I had absolutely no intension to recreate "live" the arm).
be the Force (the dark option) with you all.…
s for some solution "as it is" no matter the cost? (that's an extra stupid approach, very old fashioned). Do you use EvoluteTools Pro and/or Kangaroo for "optimization" ?
2. What is the FEA/FIM stuff in use? Do you expect "from/back" interactions? (If this is not doable ... increase this or that etc etc).
3. Do you validate real-life components with FEA/FIM? By what means you design these components? - present and/or future (inside Rhino?). This makes things "interesting" in a variety of ways (we need to extensively talk about that - Skype). The problem is that Rhino IS NOT a feature driven solid modeling app and thus ... a "certain" bottleneck arrives in no time: In the CATIA world you design ("MANUALLY") a parametric history driven component that "complies" to his parent "directives" (say: the Topology) and/or "imposes" his rules to his parent. This is what we call top<>bottom design approach (would become a standard across the AEC industry pretty soon: in around 123 years give or take some). This is far and beyond from what Rhino can do - but we DO make real-life things don't we?
4. Are all these things under a BIM umbrella ? What BIM? What type of details (blue prints) you deliver? (or you just make the thing?).
5. By what means cost is restricting/encouraging the solution? By what means you get feedback from component(s) cost that is outsourced? (i.e. outside your company). Do you monitor all things via some RDBMS? (that's Data Base).
6. What are the long term plans for dealing with such solutions? Using what apps (even in theory for the moment).…
ions - essentially Shape Changing. Pufferfish mainly uses parameters and factors for inputs for more custom control over operations like tweens and grids as opposed to grasshoppers usual division count inputs. These components are accompanied by support components which are useful methods for tween / blend / morph / lattice operations such as making curves compatible, a custom curve graph mapper, and a multi-threaded morph to twisted box. In addition, there are extra components which simplify some common grasshopper operations such as testing for equality within a tolerance and rounding to nearest numbers. Please email me if you find any bugs. Works with Grasshopper for Rhino 5, Rhino 6, Rhino 7 WIP, and Rhino Mac.
Instagrams: @ekimroyrp & @designmorphine
Download:www.food4rhino.com/app/pufferfish…
Added by Michael Pryor at 2:23am on October 17, 2017
Just spend 10 minutes watching youtube tutorial of Vray 3 and repeat:
https://www.youtube.com/watch?v=fRWANWkTouY&t=191s
Else-wise you will not learn anything and spend 10x more time because you do not know what you are doing...
For plants you can download textured proxies from here:
http://www.food4rhino.com/app/scatter
Grasshopper vray integration is also straight forward.
Chaos group did good job for user friendly interface.…
emble machines (and require custom Articles for specs, cost pre-estimation and the likes).
Putting yourself against that "forest" you should answer the question N1: you want to just use (the unsafe option) these or cross the Rubicon and collaborate in some way with the software vendors? (the safe option plus numerous benefits: knowing what's in the pipeline years ago, solving bugs in no time etc etc etc).
The question N2 is: do you get involved (or you want to) in "developing" all that the one way or the other? If yes using what "platform"? (so to speak).
The question N3 is: what are your estimations concerning the future in our trade? (count the tremendous acceleration of things as well plus the unavoidable AI factor (sooner or later)).
By answering these 3 ... you can easily answer the other questions of yours.
Bad news: future is past already.…
subsequently able to retain a higher level of flexibility.
In Rhino however a rectangle is defined as only a plane and two numeric intervals (one for x, one for y). The possible solutions to this would be:
Extend the Rhino SDK Rectangle3d type to include constant radius fillet corners. This can be done, but is a lot of work and will break the SDK.
Create a new type in Grasshopper which is smarter than Rectangle3d. This complicates developing for Grasshopper because now you have to keep two different types in mind whereas before only one was needed.
Remove the Fillet Radius input from Rectangle components. I like this solution because it results in cleaner, simpler code, but it does mean people may need to use two components where before one was sufficient.
Make the Rectangle type smart enough so that it can recognise filleted rectangles and undo the filleting. This is something I can do right now for Grasshopper 1.0 and it in all likelihood would not break actual existing files even though it is technically a behavioural change.
I'll try and get (4) done for Rhino 6 SR1, I might decide to do (3) for Grasshopper 2.0. I sincerely doubt that (1) will ever get done and I dislike (2).…
Added by David Rutten at 4:38am on November 6, 2017
er utilities for dealing with meshes , it also make ease of using voxels in Grasshopper .Yellow contains 40 components in four tabs : Deform , Refine , Utilities , Voxel . it has made easy to create various shapes by adding some deformer componenets that also work in all cordinates simultaneously. some of utility components are directly compiled rhinocommon methods in latest version of Rhino like: Mesh patch , Mesh fill holes so they only work in Rhino 6 . There's also been tried to enable most of subdivision schemes in Yellow like Kobbelt , Butterfly , Loop , ...
Yellow V1.0 makes use of the Plankton halfedge mesh library by Daniel Piker and Will Pearson, released under the terms of the LGPL license (https://github.com/meshmash/Plankton) .
Yellow has been tested in both Rhino 5 and 6 , but you may face minor bugs and you're so welcome to report them for correction. also any suggestion for making Yellow a better plugin is appreciated .
DOWNLOAD @ food4rhino…
Added by Amir Habibi at 2:19am on September 21, 2018
is a set of 188 components which focuses on Tweens, Blends, Morphs, Averages, Transformations, & Interpolations - essentially Shape Changing. Pufferfish manily uses parameters and factors for inputs for more custom control over operations like tweens and grids as opposed to grasshoppers usual division count inputs. These components are accompanied by support components which are useful methods for the preparation of tween/blend operations such as making polylines compatible and matching surface structures. In addition, there are extra components which simplify some common grasshopper operations such as testing for equality within a tolerance and rounding to nearest numbers. Please email me if you find any bugs to help make this toolset better. Works with Grasshopper for Rhino 5, Rhino 6, and Rhino Mac. Pufferfish is written in C# as a .gha file.…