Hi,
I am right now on vacation, for two weeks. I have some guesses about the issue, but without access to a proper development environment, I can't test them. I hope the guesses will be helpful:
First of all, what kind of coroutine do you use (what do the coroutine awaits for?)
3-4 frames is indeed too much. Maybe what happens is that you modify two properties of the spline, A and B. B is somehow tied to the value of A. So when you set B, A's modification wasn't considered yet in the spline internals. So basd on this guess, try refreshing the spline after each modification of the spline. It's overkill, but it might pinpoint what exactly goes wrong.
The next curvy update, that I unfortunatly couldn't finish before going on vacation, wil contain changes that will reduce the amount of state inconsistency between when a spline is modified through the API, and the moment it is Refreshed. I hope it will fix your issue. To make sure it, does please send me a reproduction case so I can debug this.
The main other addition of the next version will be big improvement in performances mainly for real time spline modifications.
I am right now on vacation, for two weeks. I have some guesses about the issue, but without access to a proper development environment, I can't test them. I hope the guesses will be helpful:
First of all, what kind of coroutine do you use (what do the coroutine awaits for?)
3-4 frames is indeed too much. Maybe what happens is that you modify two properties of the spline, A and B. B is somehow tied to the value of A. So when you set B, A's modification wasn't considered yet in the spline internals. So basd on this guess, try refreshing the spline after each modification of the spline. It's overkill, but it might pinpoint what exactly goes wrong.
The next curvy update, that I unfortunatly couldn't finish before going on vacation, wil contain changes that will reduce the amount of state inconsistency between when a spline is modified through the API, and the moment it is Refreshed. I hope it will fix your issue. To make sure it, does please send me a reproduction case so I can debug this.
The main other addition of the next version will be big improvement in performances mainly for real time spline modifications.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.