dro). The quality of the driver is also critical: hard to imagine NVidia working overnight to fix "some" driver bugs due to requests from gamers. Game cards are notoriously bad in dual monitor configurations.
3. A zillion of cores (triumph of marketing VS common sense) divided by the given clock rate ... gives you just ONE poor old core (Rhino/gh are single-threaded apps) that tries to do the job.
4. Single Xeon E5 2xxx V3 (the higher the clock the LESS the cores = better) would be my recommendation. ECC fast memory is also a must.
PS: Find a friend who operates a "loaded" H/P Z840 and test your defs.
…
of lines, etc) but I can't see a way to add the text I need where I need it. If I could get each line for the print run to generate automatically, I can put the rest in manually, so just need something like:
... ; I would do the previous to this manuallyG1 X10 Y5 Z3
G1 X5 Y5 E5
G1 X5 Y15 E10
... ; I would do the rest manually
for a 5 mm line from [10, 5, 3] to [5, 5, 3], followed by a 10mm line from there to [5, 15, 3]. Any pointers greatly appreciated.
Ewan…
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
est of the best)
Crucial DDR4 2133 ECC (what else?)
4* WD RE 500 in Raid combo (not shown)
Some stupid 2.5'' HD thingy (avoid 2.5'' disks)
No SSD thingy
Corsair CPU cooler (Tequila replaced the OEM liquid: it works)
…
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.…