Sergey Sharybin
473eff2df8
Based on an user feedback, previous implementation with providing decoupled X and Y speeds didn't work in production at all: there is no way to combine this speeds to an usable vector. So now we're providing speed vector output instead, which provides speed in an exactly the way Vector Blur node expects it to be: first two components is a speed from the past, second two components defines speed to the future. Old behavior can be achieved by RGBA separating the speed output and using first tow components. Now this speed gives quite the same results as a speed pass, with the only difference that track position speed uses "shutter" of 1 while pass uses shutter of 0.5 (and there's no way to affect on that?).