setting custom bounds to 0 now disables them (for x1,x2,x3)