02-26-2024, 09:49 AM
Hi
In the following, I will use the expression "my splines" to express the spline calculations implemented in Curvy Splines, that are then used by the tools include in the asset (controllers, mesh extrusion, etc.)
Making Curvy Splines' tools build on top of Unity's splines instead of my splines is seemingly a good idea, since it removes the burden of maintenance of a the spline calculation.
The issue is that Unity's splines is lacking features compared to my splines, such as compatibility with B-Splines.
Another point to consider is that Unity did not lately show high reactivity when it comes to fixing bugs. So if Curvy Splines relies solely on Unity's splines' API, there will surely be situations where the latter will have bugs, which reflects on Curvy Splines, but for which I can do nothing, besides reporting the bug and waiting. Same reasoning when it comes to implementing new features.
Supposing that Unity is reactive, and their splines are feature equivalent to my splines, then replacing the splines is still not a clear win, since the replacement process takes man-hours that could be more useful implementing new features.
The transition would make sense only if, in addition to the above, Unity splines add useful features missing my splines.
In the following, I will use the expression "my splines" to express the spline calculations implemented in Curvy Splines, that are then used by the tools include in the asset (controllers, mesh extrusion, etc.)
Making Curvy Splines' tools build on top of Unity's splines instead of my splines is seemingly a good idea, since it removes the burden of maintenance of a the spline calculation.
The issue is that Unity's splines is lacking features compared to my splines, such as compatibility with B-Splines.
Another point to consider is that Unity did not lately show high reactivity when it comes to fixing bugs. So if Curvy Splines relies solely on Unity's splines' API, there will surely be situations where the latter will have bugs, which reflects on Curvy Splines, but for which I can do nothing, besides reporting the bug and waiting. Same reasoning when it comes to implementing new features.
Supposing that Unity is reactive, and their splines are feature equivalent to my splines, then replacing the splines is still not a clear win, since the replacement process takes man-hours that could be more useful implementing new features.
The transition would make sense only if, in addition to the above, Unity splines add useful features missing my splines.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
