09-18-2021, 10:54 AM
Try adding a log of vec3 after you call the vec3.Set method. Maybe it is the one that changes the coordinates, and not Curvy.
This code uses classes that are not available to me (PoolBoss), so I can't run it. What I suggest to you is to create a new script, to use in a new scene, that does only the vec3 setting and the control point adding. If you managed to reproduce the issue with this simple setup, then you have a reproduction case to send me (scene and scripts). If the issue does not appear, then you know the problem comes from the difference between the real case and the simple reproduction case. You can then iteratively make the reproduction case more and more complex until it becomes the same as the real case. In that process, you will find what line of the code exactly creates the issue.
This code uses classes that are not available to me (PoolBoss), so I can't run it. What I suggest to you is to create a new script, to use in a new scene, that does only the vec3 setting and the control point adding. If you managed to reproduce the issue with this simple setup, then you have a reproduction case to send me (scene and scripts). If the issue does not appear, then you know the problem comes from the difference between the real case and the simple reproduction case. You can then iteratively make the reproduction case more and more complex until it becomes the same as the real case. In that process, you will find what line of the code exactly creates the issue.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.