some i7 if ECC memory sounds an oddity to you). If the model is big you'll need a decent Kepler Quadro as well ... say a K4200 (I hate game cards including Titan).
http://www.tsplines.com/
Alternatively use a top dog subdivision app (Modo eats them all for breakfast) but that works with DX and that brings us back to game cards.…
g these times itself). If it works on selection alone, it would probably implement faster.
Theoretically, does this mean the total solving time of the definition is the 'chain of components' that takes the longest time? In the picture above, it would be the chain consisting 'point-curve-divideDistance'?
Because that still adds up only to 97%, I am assuming the Point and Slider component start solving in parallel, and the two Divide components also start solving in parallel?…
t it is rounded to 25, 100, 75. I've figured out the rounding portion, but when I plug the resulting list back into the custom preview, it doesn't recognize the data. I'm guessing it is because my rounded list is in curly brackets, whereas the unrounded data straight from the image sampler is not. How can I process this to remove the curly brackets?
Thanks,
Ryan
…
Added by Ryan Dirks at 5:20pm on September 18, 2014
tecture. Hochbau | University of Innsbruck . A simple random, but at the same time organised growth routine. 5 iterations for this image.
Link to the course here:
http://www.exparch.at/index.php?option=com_content&task=view&id=1054&Itemid=87
View full size...as per Pieter's suggestion…
omponent that increases in the x-axis (example below).
A1 A2 A3 A4 A5 etc...B1 B2 B3 B4 B5 etc...C1 C2 C3 C4 C5 etc...D1 D2 D3 D4 D5 etc...
This is as far as I've gotten:
I have collected my points on the grid into a "List Length" component and input that into a "Series" which input into a "Function" with the expression Format("A{0}",x). The result labeling resembles the example below.
A1 A2 A3 A4 A5
A6 A7 A8 A9 A10
A11 A12 A13 A14 A15 etc...
Any help is appreciated.
Thank you in advance.…
I don't think I know what you mean. If it is that you want the curve numbers written out as text tags, use the reworked example below and adjust it to your needs.
/Ola
old version that has been fixed by now. I'd ask you to test this on the Rhino6 beta (which I am using to test this), but it looks like you're using a cracked version of Rhino so you probably don't have access to that.…