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 - CoreTech |
|---|---|
| Affects Versions | 5.3.2 |
| Target Fix | 5.6 |
| Fix Commit | 39557562 |
|---|
| Created | Feb 12, 2024 |
|---|---|
| Resolved | Jan 29, 2025 |
| Updated | Jan 31, 2025 |