Hi,
You used the word "replaced", but just to make sure: did you remove the old folder before important the new version?
If so, what was the version you had before? And what error messages do you have?
About upgrading guide, there is none, but before releasing any breaking change in Curvy, I mark the API method that will change as Obsolete, while providing the new alternative. The Obsolete tag displays a compiler warning when compiling the code, and often I add to it a custom message saying what method to use instead. So for someone who updates regularly, and acts accordingly when seeing a compiler warning from Curvy, the upgrade is done smoothly.
But for someone who had not upgraded for a long time, then this process becomes problematic. Ideally, the Unity asset store would allow owners of a specific asset to get all the older updates, but this is unfortunately not the case.
So once you will answer my questions, I would either tell you what to do if it is just few issues to fix, or I will send you consecutive versions so that you update gradually and little by little fix things. This last scenario would be needed only if it has been really a long time since your last update.
Also, as stated in the release notes page, Curvy is using the versioning standard “Semantic Versioning 2.0.0” (more about it here : https://semver.org/) which means that between a version 5.x.x and 6.x.x there are breaking changes.
You used the word "replaced", but just to make sure: did you remove the old folder before important the new version?
If so, what was the version you had before? And what error messages do you have?
About upgrading guide, there is none, but before releasing any breaking change in Curvy, I mark the API method that will change as Obsolete, while providing the new alternative. The Obsolete tag displays a compiler warning when compiling the code, and often I add to it a custom message saying what method to use instead. So for someone who updates regularly, and acts accordingly when seeing a compiler warning from Curvy, the upgrade is done smoothly.
But for someone who had not upgraded for a long time, then this process becomes problematic. Ideally, the Unity asset store would allow owners of a specific asset to get all the older updates, but this is unfortunately not the case.
So once you will answer my questions, I would either tell you what to do if it is just few issues to fix, or I will send you consecutive versions so that you update gradually and little by little fix things. This last scenario would be needed only if it has been really a long time since your last update.
Also, as stated in the release notes page, Curvy is using the versioning standard “Semantic Versioning 2.0.0” (more about it here : https://semver.org/) which means that between a version 5.x.x and 6.x.x there are breaking changes.
Please consider leaving a review for Curvy Splines, this helps immensely. Thank you.