20-06-2019, 10:08 AM
(This post was last modified: 20-06-2019, 10:21 AM by josemendez.)
Hi all,
Some of you have been having issues running the CharacterCloth sample scene from ObiCloth in Unity 2019.1 or above. Specifically, Unity spews out the error "Bone weights do not match bones" when running the scene. All other Obi assets are unaffected by this.
Since reports were inconsistent at first (some users got it to run, some others didn't), it took some time for us to get to the bottom of the issue. However the rabbit hole went much deeper than we expected.
Technical explanation ahead, scroll to the end of the message to see what we're doing to fix it.
The culprit is a seemingly innocent (and undocumented, afaik) change in 2019.1 : SkinnedMeshRenderers no longer accept an empty bone weight array.
In 2018.x we were setting the weights array to null in order to deactivate the built-in skinning, then handing over the mesh to our own library to perform custom skinning/simulation blending. Thing is, this is no longer possible and results in Unity throwing an error. We've asked if this was an intentional change and it is, so they're not changing it back to the way it was. Passing a full array with all weights set to zero does not work either, as they now enforce all weights summing up to 1. Long story short, we have to rewrite most of our system from scratch to separate bone skinning (which would be done by Unity) and simulation, then blend them together somehow.
On top of that, we switched the asset store version information to reflect that ObiCloth is not compatible with 2019.x (they let you specify compatibility per-version). However due to a bug (feature?) in the asset store, it only shows "2018.1 or higher". So we've added a warning in the asset description stating that for the time being ObiCloth is only fully compatible with 2018.1 - 2019.0, but it hasn't been approved yet so people are still downloading it for >=2019.1.
End of technical explanation
All in all, this has been a pretty disastrous event for us and we're working as fast as we can™ to fix it. We honestly expect Obi to come out the other side better, faster and easier to use than ever. While we work to make this happen, please accept our deepest apologies. We will write a blog post shortly to give you a heads-up on the development process.
To try to amend the damage caused, we're accepting refund requests from anyone that purchased ObiCloth after April 16th, the day Unity 2019.1 was released.If this is your case, please let us know by writing to support(at)virtualmethodstudio.com and stating your Invoice Number (found in the .pdf invoice sent by the store upon purchasing).
kind regards,
Some of you have been having issues running the CharacterCloth sample scene from ObiCloth in Unity 2019.1 or above. Specifically, Unity spews out the error "Bone weights do not match bones" when running the scene. All other Obi assets are unaffected by this.
Since reports were inconsistent at first (some users got it to run, some others didn't), it took some time for us to get to the bottom of the issue. However the rabbit hole went much deeper than we expected.
Technical explanation ahead, scroll to the end of the message to see what we're doing to fix it.
The culprit is a seemingly innocent (and undocumented, afaik) change in 2019.1 : SkinnedMeshRenderers no longer accept an empty bone weight array.
In 2018.x we were setting the weights array to null in order to deactivate the built-in skinning, then handing over the mesh to our own library to perform custom skinning/simulation blending. Thing is, this is no longer possible and results in Unity throwing an error. We've asked if this was an intentional change and it is, so they're not changing it back to the way it was. Passing a full array with all weights set to zero does not work either, as they now enforce all weights summing up to 1. Long story short, we have to rewrite most of our system from scratch to separate bone skinning (which would be done by Unity) and simulation, then blend them together somehow.
On top of that, we switched the asset store version information to reflect that ObiCloth is not compatible with 2019.x (they let you specify compatibility per-version). However due to a bug (feature?) in the asset store, it only shows "2018.1 or higher". So we've added a warning in the asset description stating that for the time being ObiCloth is only fully compatible with 2018.1 - 2019.0, but it hasn't been approved yet so people are still downloading it for >=2019.1.
End of technical explanation
All in all, this has been a pretty disastrous event for us and we're working as fast as we can™ to fix it. We honestly expect Obi to come out the other side better, faster and easier to use than ever. While we work to make this happen, please accept our deepest apologies. We will write a blog post shortly to give you a heads-up on the development process.
To try to amend the damage caused, we're accepting refund requests from anyone that purchased ObiCloth after April 16th, the day Unity 2019.1 was released.If this is your case, please let us know by writing to support(at)virtualmethodstudio.com and stating your Invoice Number (found in the .pdf invoice sent by the store upon purchasing).
kind regards,