12-24-2021, 04:37 PM
(12-24-2021, 03:16 PM)_Aka_ Wrote: Hi
About checking if a spline is straight, the easier solution is indeed to check the angle between the normals. If performance is an issue, go through all the spline's segments and use the CurvySplineSegment.ApproximationT, which contains the cached tangents. You can also use CurvySpline.GetApproximationT, but this is less optimized (will allocates arrays)
Regarding the reported issues with Optimize. I have to check individually the issues you reported, which I will do early next week. But what I can say for now is that some features are indeed impacted by the Optimize option. The Split feature is one of them that I am already aware of. Will say more about this subject early next week.
Have a nice day
Hi Aka,
Thanks for , as usual, your quick response. I will explore straight evaluation with the ApproximationT
In regards of the "optimize" functionality, there is no rush. Whenever you have time let me know. As I previously mentioned the possible work around is to disable optimize if the spline is straight (not ideal, but not deal breaker either) . Just wanted to put it in your radar and let you (or anybody else facing this issue) know a possible workaround.
Thanks for your great support.
All the best
Mario