algorithmic modeling for Rhino

Hi All,

I am working on a gradient tile pattern with grasshopper (actual tiles for a floor plan)

Using the great tutorials from formularch I am able to create a tile layout that i influence with curves or points (tiles close to the curve get shape A tiles further away get B etc.)

Thus far everything is great, however... all shapes get grouped under the move function, so when baked i end up with all shapes in one layer. This is not ideal. I would like to split the list so i have one function for (in this case) triangles, one for squares and one for circles.

I have tried different ways of culling and dispatching the shapes but all to no avail...

Any suggestions?


Views: 322

Reply to This

Replies to This Discussion

This works purely on number of edges so It would not distinguish rectangles from squares:


its a start :)
I actually intend to use only squares tiles, so after baking i can assign tiles to the correct material (stone A = material A) and get a visualisation of the actual tile pattern...


Hi Thomas, I agree with Danny that Sift is the key component here, but I would use it earlier on in the definition.

I am getting somwhere with this, however my shift pattern doesn't accept inputs higher than 1... "1. Filter index 2 is too high, data will be discarded entirely"... with pieters example i can get two patterns extracted, however they are somewhat distorted... 

wait... i can zoom in on it :S sorry...

Got it!

Thanks a lot!






  • Add Photos
  • View All

© 2020   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service