10-05-2019, 07:08 AM
(This post was last modified: 10-05-2019, 07:16 AM by josemendez.)
(09-05-2019, 10:59 PM)witskho Wrote: Hey. The same error when trying to work with the skin in 2019.1. Removed ticks from all optimizations in import settings, made 128 weight values, does not help. When I use a standard unit cloth everything works well. Did any specific solution appear?
Make sure you regenerate the topology and reinitialize the cloth after making these changes.
Some further clarification as to why this happens: FYI, it is not *required* to disable optimization, or to change weight values. Only re-generating the topology and re-initializing is needed. This is because all mesh import optimization does is reorder vertices/faces.
At initialization time, Obi generates an internal array that maps from mesh vertex index to particle index. This array is serialized with the gameobject, to avoid having to re-calculate it at runtime. It is used when updating the mesh at the end of each frame, so that it matches the simulation: each mesh vertex is set to the position of its particle.
In 2019, Unity changed the vertex/face order of all imported meshes by default. Not at all happy with this decision they took. This means that any functionality that relies on consistent mesh vertex order between versions (such as mesh-particle mapping in Obi) needs to re-generate this data in 2019, since the old vertex order and the new (2019) vertex order are no longer the same. This change in Unity breaks backwards-compatibility in a lot of functionality and user data in other projects that I've seen: Terrain editors, vertex painting tools, mesh editing tools, character skinning tools... luckily in Obi, only a reinitialization is needed (could be worse).
From our side, we could either completely drop support for 2018 (not happening yet) or warn our users to re-initialize cloth/softbodies in case they're using 2019. We decided the latter, even though it means a lot of user support overhead for us (and some bad reviews in the store).