We've had two reports on UDN where FInterpCurve<T>::FindNearestOnSegment returns either "NaN for the final value in the DistancesSq array during the first Newton iteration step."
The licensee on one of the UDNs mentioned [Link Removed] as the change that introduced those issues.
See the report in the 2nd UDN here:
[Link Removed]
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-206498 in the post.
0 |
Component | UE - Foundation - Core |
---|---|
Affects Versions | 5.3.2 |
Created | Feb 12, 2024 |
---|---|
Updated | Oct 1, 2024 |