David's past 2 to the 12
then me 2 to the 11 ( I need a life)
I'd say you're a shoo-in for 3rd with 2 to the 10
After that it gets a bit hazy, probably Luis then Giulio. But who's counting :)
Hi Rassul,
I think you need to subtract 1 from the input to the SDivide component's UV inputs as you are getting 10*10 = 100 subsurfaces and 11*11 = 121 image samples
)
3. KeyError(1417,)
4. KeyError(1417,)
5. KeyError(1417,)
6. KeyError(1417,)
7. KeyError(1417,)
8. KeyError(1417,)
9. KeyError(1417,)
10. KeyError(1417,)
11.......
i tried different weather file but also same result. it seems i have same problem. the file am working on is the radiation file i took from the examples . whats seems to be the problem?
thank you for your time…
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014
simplified in the bake name attribute and on the bake object component. I was counting on maintaining that structure.
{0;4}
{0;4}
{1;2}
{1;2}
Easily fixed with an additional attribute. Just curious on the behavior. Thanks.
…
Added by japhy to EleFront at 3:18pm on October 9, 2017