algorithmic modeling for Rhino

Views: 2016


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

Join Grasshopper

Comment by Ángel Linares on April 30, 2015 at 9:48am

I'm a little bit obsessed with order in definitions too, hehehe. I guessed that but it would be very nice to have them as customizable native components.

Off topic: The sub-canvases idea was one that I suggested some time ago arguing that the linear (left to right) gh definition growing logic clash directly with an efficient workflow with big definitions (limited with the one-core only support too).

Comment by Anders Holden Deleuran on April 29, 2015 at 6:10am

Angel: Guess I'm a bit of a stickler when it comes to keeping definitions "clean" :) Those are just scribbles and a line loaded from Rhino by the way. But yes, some super-system of groups might be an idea (sub-canvases maybe?).

Greg: Great to see you onboard, loving those gifs as you well know ;) Michel and I were discussing some ideas for how to better deal with connecting the various modelling environments. Should talk soon..

Alexander: Thanks, that's correct. The width of the knitting machine was a pretty hard constraint, so getting every little bit into the knit bounding box was crucial.

Comment by Alexander on April 24, 2015 at 10:50pm

This is great. Very believable. That end bit with galapagos.. Are you just matching a best fit rectangle? Maybe for fabrication? Thats a fun solution if so.

Comment by Gregory Quinn on April 23, 2015 at 10:01am

Great stuff! And for those of you who wondered what we engineers do with Anders' geometries:

Comment by Ángel Linares on April 23, 2015 at 4:13am

Loving how you organizr the gh definition layout :) Those separation lines and titles could be a great request to David for the next release :)





  • Add Photos
  • View All

© 2020   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service