Description

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.

 

Steps to Reproduce

See the report in the 2nd UDN here:

[Link Removed]

 

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-206498 in the post.

0
Login to Vote

Unresolved
ComponentUE - Foundation - Core
Affects Versions5.3.2
Target Fix5.5
CreatedFeb 12, 2024
UpdatedFeb 22, 2024