03-23-2020, 02:14 PM
Hi,
Collisions: I don't think it is expensive for smart pones, except if you have really a lot of objects in your scene. Keep in mind that I don't have experience making smart phone apps, so I might be wrong. Regardless, if the objects you want to check collisions against are static and defined in edit time, you can save their position on the path (a value between 0 and 1) and check against those values at runtime, instead of using colliders.
Recalculate path: I don't have a solution to that. Maybe looking for "collision avoidance path algorithm" will help
Extra: Sorry, I didn't understand. You want the rotation of the last cp to be the rotation at the end point? Aren't those the same concept?
Collisions: I don't think it is expensive for smart pones, except if you have really a lot of objects in your scene. Keep in mind that I don't have experience making smart phone apps, so I might be wrong. Regardless, if the objects you want to check collisions against are static and defined in edit time, you can save their position on the path (a value between 0 and 1) and check against those values at runtime, instead of using colliders.
Recalculate path: I don't have a solution to that. Maybe looking for "collision avoidance path algorithm" will help
Extra: Sorry, I didn't understand. You want the rotation of the last cp to be the rotation at the end point? Aren't those the same concept?
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
