[Mover] UMovementUtils::ComputeAngularVelocity unlimited TurningRate regression in 5.6

Development Platform & Builds
, ,
1

Implementation of UMovementUtils::ComputeAngularVelocity has changed so that a negative TurningRateLimit no longer means unlimited turning rate (despite the doc comment and value clamping allowing this). The change in CL 37095162 caused this regression.

Attached is our fix restoring the condition from before this CL.

2

Steps to Reproduce

  1. Set TurningRate parameter to -1 in a movement mode’s movement settings
  2. Attempt to turn character instantly
3

Hey Jack,

Thanks for the bug report and proposed fix! We actually switched how we’re calculating angular velocity for 5.7 to use degrees and it includes a fix for this issue as well.

Thanks,

Nate