Oh sorry for the spam guys. Apparently all the emails with the too large attachments got approved by the moderators.
I've been looking into it more and it also occurs in 2013. There is nothing wrong with the curves being plugged, it doesn't matter which ones I plug into which port, only every other port works. And it only happens with locations from the UV to Location node. Any other location or other value like a vector or a color plugged in, in it's stead works great. Has this bug been logged previously? On Fri, May 31, 2013 at 1:59 AM, Leonard Koch <[email protected]>wrote: > Hi Guys, > > I ran into a weird issue. > > When plugging a series of locations from UV to Location nodes into a > select case node only every other port works. > This is shown in the image "SelectCase_UVToLocation_ScalarPerPoint". > > As illustrated in the attached images, This only happens however if both > the 2D vector you plug into the UV port of the UV to Location node and the > integer you plug into the condition of the select case node, are in a per > point context. > This is shown in the image "SelectCase_UVToLocation_ScalarPerObject". > > It also does not occur if you use another location generator like a get > closest location node and plug those into the select case node. > This is shown in the image "SelectCase_GetClosestLocation_ScalarPerPoint". > > It also does not occur if instead of a select case node you use a build > array node and a select array node. > This is shown in the image "BuildArray_UVToLocation_ScalarPerPoint". > > From this we can conclude that the weird behaviour only appears between UV > to Location and Select Case nodes in combination. > > Version is 2014. > > The BuildArray alternative works for this simplified scenario, but doesn't > suffice for the actual tool set. > It is also a lot slower since all locations instead of just one have to be > evaluated. > I would write my own node, but unfortunately Locations are off limits for > custom ice nodes. > > Either this is a rather nasty bug or I'm missing something. > Does anyone have an idea as to how to handle this? >
