GetSlice (Node) bug in conjunction with filetexture and shader


the new (beta18/binsize) GetSlice (Node) seems to have a bug when used in conjuction with FileTexture and a spreaded Shader. Despite only one texture being “getsliced” the shader also shows other textures out of the connected spread of textures. Doesn´t happen if I use a quad instead of the shader .
Problem does not occur either when using beta17. See attached patch for details. (285.4 kB)

Ok if the index pin of the getslice is spreaded there are also problems when using the quad. when playing arround with the bin size it gets even weirder.

hi bjoern,

thx for reporting this bug. fixed in beta > 18