I was wondering if we could fix that bug by actually editing the engine code and submitting a fix.
If the bug has already been fixed, then could we go over what the bug was and how it was fixed?
Wasn’t exactly a bug with the engine, first of all ESuggestProjVelocityTraceOption::DoNotTrace is not the default parameter, ESuggestProjVelocityTraceOption::TraceFullPath is and secondly it was concluded that the failed traces were a result of floating point rounding and if you wanted to use TraceFullPath then to add a small amount to the Z value of HitLocation
https://answers.unrealengine.com/questions/435995/suggestprojectilevelocity-behaving-badly.html