Hey and ! Thanks for the update on this. Let me ask, is it possibly a bug then if you have widget component for example that is attached to the camera and you rotate that camera with it as the primary view target? When you do, the component attached I would think since its relative to the camera would possibly cancel out the velocity all together since it also doesn’t move in screen space technically. However, it blurs almost to the max extreme but I have also even noticed a slight jitter as if the child component is like a frame behind when updating its wvp matrix. If that were true, it could be creating inconsistent velocity data I would think. Maybe this is contributing to it and boils down to an issue with when the children matrices are updated for the current frame. Maybe I’m wrong on this but if you are saying anything that shouldn’t be moving in screen space wouldn’t contribute velocity data, then its likely this could be the culprit of that. Just wanted to check on it anyway just in case because this is an important feature to 2 projects I’m working on. Thanks guys!.