05-01-2021, 08:17 AM
Hi
I believe this is due to how the normals and tangents are computed in Curvy: instead of implementing a tangent and normal formula for each one of the spline types supported by Curvy, a single method is used for all of the spline types which is based on the spline points' position (interpolation) formula. Unfortunately, the downside of this method is that, when building a normals cache (what is displayed in your screenshot), its precision depends on the cache density.
I am intending to eventually change the tangent/normal computing code to have a more precise, per spline type code, but until then, you can avoid this issue by increasing the cache density.
I hope this help
Please let me know if I can help further
Have a nice day
I believe this is due to how the normals and tangents are computed in Curvy: instead of implementing a tangent and normal formula for each one of the spline types supported by Curvy, a single method is used for all of the spline types which is based on the spline points' position (interpolation) formula. Unfortunately, the downside of this method is that, when building a normals cache (what is displayed in your screenshot), its precision depends on the cache density.
I am intending to eventually change the tangent/normal computing code to have a more precise, per spline type code, but until then, you can avoid this issue by increasing the cache density.
I hope this help
Please let me know if I can help further
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.
