algorithmic modeling for Rhino
Hello, I have created a mesh in kangaroo, and a set of intersecting lines in hoop snake. I have attached these lines to the mesh. Now I would like to add thickness and smoothness to the curves but exoskeleton doesn't work properly because nodes aren't readable properly as in the file "1".
Do you now how can I achieve such effect as shown in the photo 3 in the "2" file?
Tags:
Just spotted that one.
Get these 2 as an intro to the "get lines and make a thickened mesh" puzzle.
The first (the simplest) provides 5 modes to choose anchors thus yielding a variety of "vault" type of stuff. Then it works either with ExoW (black mesh) or IntraLattice (blue mesh).
That said ExoW is tricky: occasionally reports engulfing issues and stops playing the game. For instance in this (diagonal) anchor mode and with some U/V random values:
Whilst IntraLattice appears rather less temperamental:
The other def is more complex and works using the Proximity approach that makes more sense with regard random 3d line graphs (as an exercise: Add a gate and use IntraLattice as Plan B).
OMG! this helped me a lot!! Thank you soo much :)
Moral: ExoW is the Ducati (if it works is heaven) and IntraLattice is the Honda (it works but leaves you a bit cold).
I have another question to the "2" file. Do you know how can I make a mesh from a curves I attached to the mesh made in kangaroo?
You mean that you want the replace the lines (edges) with curves ??
For instance: get a given line define a perp plane at, say, 0.2-0.8 > get the x/y axis vector > multiply by some value > get a "mid point" and then interpolate [the line start, the" mid" and the line end].
I meant from this curves
Ah that one:
1. You must split each curve VS any other (easy with C#: notify if you need a "standalone" thingy that does this).
2. Then use IntraLattice (but as we had seen: IL is not the holly grail of liquid things).
1. Forget meshes.
2. Create a FLAT random collection of lines.
3. Get all the resulting segments (as discussed above).
3. Morph these into some user controlled surface (curves) OR use K1/K2 to create a vault type of stuff (lines). Don't forget to deal with the end/start pts [as in 2] as anchor points. Using K1/2 means: springs on the segments [as in 3] AND some unary force assigned to the free to move nodes (all minus anchors).
4. Use IntraLattice.
But the big thing is that IF this is some kind of AEC (or you are an Architect) I would strongly suggest to use lines instead of curves ... since in real life ... blah, blah.
If you are an Artist ... do whatever you want.
And here's a rather stupid (and a bit kitsch) example on the split all with all theme:
Imagine a C# that does this "network" of random connections (with 6 different modes). Shown linear ones but you can have curves as well.
Then another C# makes the pieces due to Curve to Curve intersection events (all VS all or a collection VS another or some other options). Then the pieces + unary forces + anchors (no mesh around) are treated via K1 (we should use K2 for that ... but anyway) and a kitsch vault is made.The fact that there's no triangulation ... makes it more pointless (planarity + beefier nodes + ... > further and further away from any engineering neatness etc etc).
Obviously with some interactive ability (C#) to define specific anchor points "within" the middle of the network ... we can transform the kitsch to wow in no time ... meaning that the possibilities are endless.
If the network is made via curves we need some target surface to morph it and then use IL.
In fact these things in real life are made via some proper system the likes of MERO KK or some tensegrity truss or some complex hybrid involving planar glazing etc etc ... but that's another story.
You can also use weaverbird! I got the image below from pinterest
BTW: Did some tests (flat random curves > split all > map to some Surface > IntraLattice).
For instance (all Curve segments are split at any Intersection Event):
Problem is that this type of random approach can hide nasty surprises (unpredictably small pieces that make IL life rather difficult):
And if we are out of Karma (the norm) this is what IntraLattice does (an invalid mesh plus some oops stuff: all "mesh portions" starting from 0,0 [rather unwanted, he he]):
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by