06-01-2018, 02:30 PM
Thanks for the reproduction scene.
This is fixed in the update I am preparing. The actual fix is based on code that is drastically different than the code in the current Curvy version (2.2.4.2), so I can't simply extract the fix and send it to you. So the best solution is to wait for the update.
If you need a solution right now either:
- give your controller some very small but not 0 zero.
- or remove all occurrences of "&& (Speed != 0 || mForceUpdate)" in Assets\Packages\Curvy\Base\CurvyController.cs (might create undesired side effects)
This is fixed in the update I am preparing. The actual fix is based on code that is drastically different than the code in the current Curvy version (2.2.4.2), so I can't simply extract the fix and send it to you. So the best solution is to wait for the update.
If you need a solution right now either:
- give your controller some very small but not 0 zero.
- or remove all occurrences of "&& (Speed != 0 || mForceUpdate)" in Assets\Packages\Curvy\Base\CurvyController.cs (might create undesired side effects)
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
