gone with the wind topic: since this is utterly Academic the main issue here is to oversimplify LBS (in real life: a collection of columns/beams/slabs/X members + tube frame rigid members (shafts/elevators/cats/dogs)). Reason is that if we use the real "solids" (turned into meshes) as the "node" pool for the hinges required ... only HAL 9000 could solve it in "real-time" (for instance an E5 Xeon 1630 v3 takes ... several minutes). And this is ... er ... challenging I must say. This is a typical case where "simplifying" means "stupidity" almost instantly.
Spam on:
where's my collection of "bend-a-truss-that-looks-like-a-tower" K1 demo defs? Is in this workstation or in another? (blame Alzheimer).
Spam off.
More soon.…
I have a database with about 80 tables on it, so i wanna connect to the database, make 5/6 different queries, extract the info and use it as an input to grasshopper.
rasshopper and reinstall it every time because I've seen this problem before in forums but no one ever came up with a fix. Edit:Another weird leak is when I close rhino and grasshopper now even that I had stable low memory usage before closing. Process Rhino.exe is till running and climbing in memory and reached 97% even the program is shut down.Edit2: My gut feeling is that when a component reaches certain branch/item number it starts leaking memory. And specifically recent file/ MRU list is doing the leak…
0%3ATopic%3A160646&page=1#comments
I was trying to update the old VB component to my new 0.9.0006 GH release, copying and pasting, but as I'm new in this scripting world I'm unable to solve the error bounced at the line 97 when I link the surface component.
Any suggestion??
thanks in advance!!
…
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…