i’ve found this issue using the gradient component in a very simple definition but i cannnot find why y doesn’t fill with correct colors these areas.
Element 26 is the smallest area of this multiple curves, as seen on panel, and when i use the gradient it gets color 255,255,255 (white) but on the screen colors seem to work in another way
April 29, 2019, 11:37am
Are all of your curves definitely closed?
If you can upload your definition, internalising any geometry referenced from Rhino, it will be easier to help.
Here’s the definition
Crvs are closed and planar
12lab_area.gh (15.5 KB)
April 29, 2019, 11:46am
I think the t value may need to be a floating point number between 1 and 0, but not 100% sure. Remapping the numbers seems to do the trick.
Edit: just tested and it doesn’t have to be a floating point, so I dont know why your definition isn’t working.
12lab_area_V2.gh (12.8 KB)
I´ve tried remapping but checking panels elements 15 & 26 are the biggest and smallest, they should be white and black
don’t know what happens…
I found the error…
when i converT crvs into srf the index changes…
@DavidRutten @DanielPiker ?
April 29, 2019, 12:36pm
I just noticed the same. I have never seen this behaviour before…its a little worrying.
April 29, 2019, 12:42pm
This is actually (reasonably) expected behavior. Note that Boundary Surface accepts a
list of curves - in order to handle cases like shapes with holes in them, boundary surface processes all the curves it gets in a list at once - and there is no guarantee of a 1:1 mapping between the original curves and the output surface order. Just graft the input to Boundary surface and flatten (or shift paths / trim tree) out the other end to ensure the order is consistent.
@andheum it worked like a charm…