Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Looping splines and GetNearestPointTF
Small feature request:

Make GetNearestPointTF handle closed splines better when supplying start/end segment indexes.
Current implementation clamps start and end index and also requires that the end segment index comes after the start segment index. When working with closed splines, it would be nice to be able to supply start/end indexes such as start = 5, end = 1 when searching near the spline wrap-around.

In our case we try to find the closest position, but due to level layout (our spline crosses itself at some points) we want to limit the search space to only consider segments that are "near enough". But with the current implementation of GetNearestPointTF we need to do some special case handling when the player is near the wrap-point on the spline, basically implementing our own version of the method.
Hi TurboHans
You have a very good point there. Your feature request is noted. Will update this post when it will be actually implemented.
Have a nice day
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.

Possibly Related Threads…
Thread Author Replies Views Last Post
  Error when recreating splines / connections jh092 3 3 07-25-2022, 09:58 AM
Last Post: _Aka_
  Closed splines and duplicate points jh092 3 5 07-24-2022, 01:54 PM
Last Post: _Aka_
  Splines as/in ScriptableObjects Najati 1 4 06-05-2022, 11:12 AM
Last Post: _Aka_
  Switching splines linkinballzpokemon 3 14 04-13-2022, 04:23 PM
Last Post: _Aka_

Forum Jump: