ome day soon.
5. Ok, I'll add some easy string manipulation components for 0.7.
6. Just changed that, it will be available in the next release.
Thanks for testing and the feedback (and the praise). I can safely say that writing Grasshopper is the most rewarding thing I've ever done in my life.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
are some definitions in the 'Spreadsheet' folder to get you started. The best thing to keep in mind is that each data tree branch will act as a row in the spreadsheet. So if you have a list of 10 items, you will get one row with 10 columns. If you have 3 branches with 10 elements in each, you will get three rows with 10 columns, etc...
Best,
Luis…
rom 10 to 4. But I had no crash with either your file as is or after I made these changes.
Maybe you have an old version of Grasshopper. Or maybe your surface shape forced it into some sort of compute loop. I've found that it is almost impossible to cause an actual Grasshopper crash. …
Added by Birk Binnard at 10:29pm on February 9, 2017
opening a simple file with 30 curves being lofted took like 2 minutes to complete and Rhino crashed afterwards saying:"Windows is out of memory and Rhino will close after you click ok."evethough I still had 7GB of free physical memory and my page file is set also to 16 GB just to be shure...I then switched to Rhino 5.0 Version 5 SR14 64-bit (5.14.522.8390, 05/22/2017) which also had big problems to display the lofted surface. It was unresponsive after loading the file for a minute and a half and then it normally displayed the lofted surface. Every move of camera takes at least 10 seconds to update, but at least it runs. GH profiler says the loft took only 12 ms (90%).
So I'm suspected my graphics card, because the Windows are just three weeks from a clean install. I've also updated my Graphics Driver from the stock Windows one to Intel HD one, but nothing changed.Is there something I'm missing??? What can I try next?My specs:CPU: i5-3320M @ 2.60 GHzRAM: 16 GBGPU: Intel HD Graphics 4000, driver: 07.04. 2017, version 10.18.10.4653
…
Added by Šimon Prokop at 10:39am on October 21, 2017
3500
0;2 5000
0;3 1500
etc
this did not work, but then figured to provide 1 by 1 lists like you suggested, by duplicating accordingly E,I,As. It would be nice though the components to work on list or tree access, unless this causes problems.
An exception is the bar self weight component, which although provided an 1 by 1 lists input it outputs the following, working in cross reference i think,
my workaround was to graft inputs, flatten the output, in order to match the items one by one.
than you again
best
alex…
has 2 neighbor "faces" (excluding the "perimeter" ones).
2. This means that you probaply/actually want the pairs bisector vector (IF they are pairs around ... excluding the perimeter "faces" etc etc). Against popular belief this is not the surf normal at some point vector (but forget that: is a bit freaky).
3. That bisector thingy is the sum of the 2 (unitized) vectors: the bisector of the 2 "faces" ... so to speak.
BTW: From 1 to 10 what is your knowledge of DataTrees?
More soon …
ith a number slider. When the pont new location is OK for me (changing the slider) I update my excel file, changing only one point at a time. My problem is that when I change on point in excel, the whole update process meaning, when I see the change of one point in he geometry in Rhino window takes more than one minute.
During this time Rhino and grasshopper are freezing. Since usually I have edit several point in a geometry, which means it can take me hours to finish the job, which is absolutely unbearable.
My first question that this more than minute update time with such amount of data is supposed to be normal, or I do something wrong?
Is there a way to speed a job, maybe there is a workaround for this problem?
Thanks for any help in advance! …