Not the same problem, but I run into another issue with the update to VS 16.3. In my project I use a custom CharacterMovementComponent (just copy-paste...