rom two surface offsets. I did a merge list to create a pattern from an wavy surface. I obtained several surfaces made of two toggle boolean.
Capture%20d%E2%80%99e%CC%81cran%202016-05-18%20a%CC%80%2016.26.16.png
How can i simplify those surfaces (made of two surfaces)?
Capture%20d%E2%80%99e%CC%81cran%202016-05-18%20a%CC%80%2016.26.38.png
Also, how can i link the two offset surfaces in a closed volume?
Thank you guys!
Best,
Rémy…
me in 19 different pipeline components. Marginally better, but I'll still need to do this operation approx. 80 times...gulp.
Here's a wishlist request for David: expose string inputs in the Geometry Pipeline for Layer and Name. If I had that, I could change one string to swap my whole geometry set! (My layers have names like "B1 red rail", "B1 blue rail" etc., then the next time I'll want "B2 red rail", "B2 blue rail" etc.)
BTW, I'm happy to script something in C# if it will help: maybe I could write something like the Geometry Pipeline that takes a string input for layer name? Hmmm...
…
I have a database with about 80 tables on it, so i wanna connect to the database, make 5/6 different queries, extract the info and use it as an input to grasshopper.
gone with the wind topic: since this is utterly Academic the main issue here is to oversimplify LBS (in real life: a collection of columns/beams/slabs/X members + tube frame rigid members (shafts/elevators/cats/dogs)). Reason is that if we use the real "solids" (turned into meshes) as the "node" pool for the hinges required ... only HAL 9000 could solve it in "real-time" (for instance an E5 Xeon 1630 v3 takes ... several minutes). And this is ... er ... challenging I must say. This is a typical case where "simplifying" means "stupidity" almost instantly.
Spam on:
where's my collection of "bend-a-truss-that-looks-like-a-tower" K1 demo defs? Is in this workstation or in another? (blame Alzheimer).
Spam off.
More soon.…