Spreaded Counternode Minimum Value Bug


i think ive found a bug in the counternode. i tried to have several minimum and maximum values and count throug them individually. the problem is that just the first slice starts to count with the correct minimum value. the following slices start with any number inbetween its minimum and maximum value. (havent found out the rule where they start)

even reseting each slice manually doesnt set the slices to the correct minimum.
see the attached patch to try it out,



Counterbug.v4p (6.1 kB)

true, and negative minimum values are also not accepted …