byte-accuracy red, green, blue channels) = 27 bytes. More likely 28 bytes as colours are probably stored as 32-bit integers, allowing for an unused alpha channel.
28 * 800,000 equals roughly 22 megabytes, which is way down from 9 gigabytes. That's a 400 fold memory overhead, which is pretty hefty.
Grasshopper stores points as instances of classes, so on 64-bit systems it actually takes 64+64+3*8 = 152 bytes per point*, which adds up to 122MB, still way less than 9GB. It would be interesting to know where all the memory goes...
* Grasshopper points also store reference data, in case they come from the Rhino document. This data will not exist, but even so it will require 64-bits of storage.…
Added by David Rutten at 4:13pm on December 11, 2014
That is the [List Item] component. In the latest GH versions you can zoom in on the component and add additional outputs for +1, +2, +3 etc. and -1, -2, -3 etc.
t case point 3 should be able to move from 20 to 33
so in other word
pt 3 depends on pt 2
the problem is if i only have sliders
pt2 could be 20
and pt 3 could be 20, that is higher than 33
so the loft loops in itself
gracias por tu ayuda
salu2
m…
So u seem to have the same issue as me then? I have to explicitly change it to 0 1 2 3, the default is not this it is 0 1 3 2. Converse for a tru face it is as expected, default is 0 1 2.
Added by Steve Lewis at 7:00pm on December 24, 2013