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.…
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!!
…