Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Fixes for known issues
#1
Exclamation 
Hi everyone.
You will find in this thread the fixes to known serious issues that are awaiting to be released with the next Curvy version. I hope I will not have to post too often here Big Grin
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
Reply
#2
Issue:
UV2 (used in lightmaps) are not correct under some circumstances

Fix:
While the update with the fix is not released yet, contact me privately with your invoice number and I will send you a patched version of Curvy's files
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
Reply
#3
Issue:
The Path Relative Translation module produces a path with some invalid data, which may lead to issues when other modules use that path.

Fix:
In Curvy\Base\CG Modules\ModifierPathRelativeTranslation.cs, insert the following between lines 86 and 87: data.Recalculate();
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Compilation issues for iOS with a scene containing generators puzzlekings 2 398 05-13-2021, 06:53 PM
Last Post: _Aka_
  issues with face over lapping and generator ranges Mos Def 7 1,438 12-13-2020, 07:46 AM
Last Post: _Aka_
  Issues with generated meshes TurboHans 2 742 10-30-2020, 10:01 PM
Last Post: _Aka_
  Issues with 2018.3.0f2 douoht 9 10,198 01-25-2019, 04:46 PM
Last Post: _Aka_

Forum Jump: