GH) > then define (still in GH) some instance definition (or many: case variants) > then place it according some "policy" (3d point grid and the likes). Note: Only doable with code, mind (C# in my case).
Obviously you can skip the creation part and instruct GH to deal with instance definitions already listed in the Block Manager (say: find the block named "cell666_B3" blah, blah) ... but that means that you can only use them (meaning a rather "limited" parametric approach) and not make them from scratch (meaning a true parametric approach).
But I guess that you've tried the block way in the Rhino environment already. That said I use rather solely this approach in GH and yields quite manageable object collections - I would say "real-time" response (up to 20K instances) but I use dedicated Xeon E5 1630 V3 workstations (with NVida Quadros K4200 and up for the graphic response part of the equation) so the "performance" is rather a subjective thing.
Modifications:
easily doable with GH (on instance definitions at placing time: since you need only to scale them and not vary their topology).
Anyway post a portion of the R file.…
FORE MeshMachine (rather better) or after
BTW: For a mesh with 7M points ... well... you'll need some proper CPU to deal in a reasonable amount of time (what about a Xeon E5 1630 V3?).
Alternatively find a friend who knows very well Modo ... and see first hand what the US Movie Industry is all about.…
am doing the paneling tutorial from the first primer..pg 88. i baked it but while selecting the multiple geometries i cannot select individual ones, they are selected as surfaces..is that ok or .....?
Added by SHILPA PANDE at 6:25am on February 16, 2013
Hi Chris,
Quick response!!
Attached. There are a lot of things in there ...
I'm suspecting it can be a memory issue. I'm running at 84%, which is not critical, but ...
-A.
.' refers to all elements whose identifier starts with 'A' followed by an arbitrary character. More details on regular expressions and their syntax can be found in the Karamba manual. Regular expressions can also be used at the 'GroupIDs' input-plug of the 'Optimize Cross Section'-component.
Best,
Clemens
…
1 and A1 that define the first eye point, P1.
Then a row width and a constant value for C that define the next eye point.
Angle 2 will then give Height 2, Height 2 gives Angle 3 etc...
You can easily do this as a series of functions that follow on from each other,
but there could be a very large number of these, and also a variable number, not a great way to do it.
What I really want is three series that output numbers to define values for Distance, Height and Angle.
D can be defined as a series, but H and A need to be calculated sequentially.
A2 gives H2, then H2 gives A3 etc... One series needs to the input of the other and vice versa. Doesn't work with Logic/sets/series as you end up with circular inputs.
Any ideas on best way to set this up greatly appreciated.
Thanks.…
curve B
B1--------------------------B0
You define distances:
|A0 B0|
|A0 B1|
|A1 B0|
|A1 B1|
And find the smallest one. Then, based on the number of the shortest distance:
Flip A, Leave B
Flip A, Flip B
Leave A, Leave B
Leave A, Flip B
A more advanced metric would be to create all 4 blends, then pick the one that is shortest. Maybe that works better for what you want, maybe not.
--
David Rutten
david@mcneel.com…
Added by David Rutten at 8:09am on February 11, 2014