Grasshopper

algorithmic modeling for Rhino

So I'm trying to take a surface and perforate it with a bunch of funnels.  I need the mesh to respond to the vortexes, so that if they move, the mesh opens up for it.  I guess in a way, I've been trying to weave together two different relaxed objects.  

I'm open to any and alllll suggestions- any ideas on how to proceed.

Views: 8263

Attachments:

Replies to This Discussion

If

(a) the cones (the "columns") have one point as "contact" point you don't have to punch any hole. Just pick (randomly or wait for the Interactive_pick_items_v2 C#) mesh vertices project them into the ground connect them with lines (with a max spring value: thus vertices are pulled to the ground as far as the projections are Anchors) and then ... press the happy bunny button (the pink one).

(b) they don't ... but ... wait ... that's already addressed via the other definitions provided in the other recent thread of yours: for instance this:

BTW: For a variety of reasons IF you want a "high" mesh density (pointless) DON'T attempt to mesh a region with holes (case already provided) and then pull (as above) all the hole(s) "perimeter" vertices against the ground.  

BTW: As the case V12B proved: FIRST use K1/2 against the main members of a given structure (meaning a far controllable situation) and THEN potentially further "refine" the faces ... exactly as we do in real life 

And that is brilliant- but now i need them to intersect as separate geometries- sorta like this

except on a plane... and instead of the blue things going through existing holes, wherever the blue thing punches holes, the orange surface would perforate to give it space to go through- just like in the picture.

I think that this one sort of includes a perforation too--

So- indeed the happy bunny button is brilliant and I'm loving it, but I'm not sure how to apply it to this problem set- how can i use it to make these two puppies interact neatly?

Er ... hmm ... you never listen eh?

I've e-mailed that atrocity to the Greatest Ever (lot's of Vodka made this easy) > He said (Ref: Total Recall - the dual head chief of resistance talking to my hero Arnie S) >:  empty your mind > reset > avoid liquid nonsense (at any cost) > obey > be a happy bunny.

Mies VDR also said to me: Tell her to come to the Dark Side > White Side BAD is > What about a tour de force? A tensegrity truss that can leave mere mortals speechless  (C# only no components).

Mies also said: Never provide to her stuff like these:

Moral: Liquid bad IS (Yoda also said that).

BTW: Mies VDR also said to me: IF you have "conical" topologies in mind > use ONLY membranes.

I'm trying to empty my mind. What are you saying? ahhhh- I'm way lost, but I want to learn! 

I'm all about the dark side if Mies chills with me, so I'm learning this C# stuff as quickly as possible! It's definitely a... different... learning curve.

YES! Conical topologies-- exactly! With the same holes, simply as responsive perforations. Okay, I will try to reset and start again while just playing with meshes.

Well ... to tell you the truth I don't quite understand what Mies means (in most of times) since I'm not that smart.

But I've asked explanations by addressing an official request to the right fellas:

And ... guess what? they suggested to start walking the walk (to greatness) with this attached thingy.Have in mind that this is an entry point stuff (kids in kindergarten class) and ... well ... a totally different approach is required in order to control things (membrane topology as a whole) properly > a fact that brings us straight to the Dark Side (the only side as anyone can certify).

They also said ominous things related with C# but I have no idea what they mean since I have no idea about coding as well (all the stuff that I've provided insofar are made by my top C# gurus in my practice [I'm just the boss: I hate coding and drinking water]).

BTW: For quickly as possible you mean 10 years? (or maybe 20?)

BTW: Task for you:No R file attached > what is required in order to place some viruses? He, he

May the Force (the dark option) ... blah, blah

more soon

Attachments:

Also an entry point thingy (no cones option) that IF combined with other things (like this, this and that) could yield some stunning combos - not just one membrane that is (but how to do that? You tell me, he he).

Note: See K2 in parallel  action as well ... I mean a freaky C# thingy that replaces all the known K1 components via some freaky lines of code. This part is made by my top dog C# guru:

If you can empty your mind completely ... AND NO stuff other than the proper stuff is around (membranes, what else?)... then maybe (just maybe) I'll post the notorious V4C version ... that maybe (just maybe) can blow your mind in pieces.

BTW: Compare situations where freaky things happen (K1) VS normal things (K2).

Attachments:

This is great haha, very... architectural.

RE: BTW 1: 10/20 YEARS??! Darn, the learning curve is steeper than I thought. I've just been reading and trying to figure out basics from tutorials.  I figured some day soon it would all click and then I'd be parametric dark side modeling like it was nothing.

Re: BTW 2: What is required? Just an imported block? Right? I mean you just have to pick and place the selected virus and your fancy code brilliantly emulsifies and populates the surface?

V1 is brilliant-- way more rigger points! Maybe- BTW, super nice truss C# maker.  That's so sweet! How do you make things like that?!

Well ... to to tell you the truth all that stuff are made by THD (top hairy dog - an Architect as well) so ask him: I barely understand what he says/does in most of times: I'm just the stupid boss.

BTW: THD recommends to stay away from C#: this is freaky stuff and girls don't actually like freaky stuff (in the long term).

BTW: In order to "pass" this abstract "concept" (or any similar) to a bunch of pro BIM aps (the likes of AECOSim) and do it in real-life you'll need a lot of lines of code plus a lot of cigars/espresso plus Karma.

So I tried clearing out and starting again.  Which almost got me through a way to relax the fused meshes and create "best fit" holes in the surface, but then it was clear I was simply doing different iterations of the same thing. 

Any ideas on how best to start "weaving" or "interspersing" these? Not so much as a building, perhaps more as a form of cell life.  I can't seem to relax this mesh properly so that I can weave it around with others.

I mean, all of the vortex pieces exist independently of the panel they hit.  I can't weld them, so I can't make them move as one, as if I were using a proper kangaroo thing. 

Any any any any ideas you have would be incredibly respected and appreciated! I'm going back through the other files now to better understand what you are saying.

Thanks again!

Attachments:

Jesus! WHAT A CHAOS:

1. This is NOT a case for a novice by any means. Even if things are fixed (easy) ... you'll being trapped in the rabid hole when you attempt to "inflate" all that mess simulating some kind of "smooth" vault (Mies in despair, but vaults are ideally suited for funeral ceremonies and the likes). Why? mesh "resolution" matters that's why (cone legs are tiny VS the whole combo meaning the obvious: a mesh with 6666666666 faces > get a Cray).

2. Your top circle radius (per cone ) was greater that the Swiss cheese radius > meaning Armageddon when "combining" this with that (rather  breps > then MeshMachine against the Swiss cheese with legs combo).

2. But the main thingy here is that you have overlapping conical stuff because the random pts policy doesn't take into account this little detail. I could easily fix that:  (a) either by controlling the random points (see 3) OR (b) by doing bool ops in "cones" (as Lofted Breps) that overlap ... but my nerves are a bit broken this particular moment. The other related stuff is cones in the "outskirts" of that terrain meaning portions "outside" the OEM terrain boundary (addressing this is not nuclear science, mind).

3. And since Rhino is not exactly a Ferrari when doing Brep bool stuff (meaning Asta La Vista babe if the cones are a zillion) ... DID I or DID I not provided an "even" random point thingy that works by checking min distances? (double the drilling radius + some tolerance in this case). Why you don't use that? You tell me. BTW: I did that exactly for similar cases , you know (unless you absolutely need "fused" cones: but who can spot that? and if he could > why bother?).

  4. Other "minor" issues follow (about 6) : like this, this, this and that.

Moral: Long is the path (and hilly)

That's good if the cones intersect! It's more organic- they would just have to Boolean each other and so that they can don't overlap surfaces.

You did indeed provide a brilliant min-distance option- but this would limit the opportunity for people/viruses to mingle... and create interesting variations in the mesh.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service