04-11-2025, 11:24 AM
(This post was last modified: 04-11-2025, 02:31 PM by josemendez.)
Hi!
Glad you found the cause!
Deactivating Scene Reloading means Awake() is not called. This causes the cloth renderer to not pick up the fact that the blueprint has changed. While we do support deactivating domain reloading, we do not currently support deactivating scene reloading.
Unity's workaround for this is to use OnEnable() instead of Awake(), however this is not an option since that would reinstantiate the skinmap every time the component is disabled/enabled.
So the best solution is indeed to call InstantiateMeshAndSkinmap() if mesh data is empty, which is what your workaround does. This only instantiates the skinmap if the data has been lost due to not being serialized, and Awake() hasn't been called.
Note however that other issues might stem from disabling scene reloading, as Obi doesn't support it yet.
let me know if I can be of further help,
kind regards
Glad you found the cause!
Deactivating Scene Reloading means Awake() is not called. This causes the cloth renderer to not pick up the fact that the blueprint has changed. While we do support deactivating domain reloading, we do not currently support deactivating scene reloading.
Unity's workaround for this is to use OnEnable() instead of Awake(), however this is not an option since that would reinstantiate the skinmap every time the component is disabled/enabled.
So the best solution is indeed to call InstantiateMeshAndSkinmap() if mesh data is empty, which is what your workaround does. This only instantiates the skinmap if the data has been lost due to not being serialized, and Awake() hasn't been called.
Note however that other issues might stem from disabling scene reloading, as Obi doesn't support it yet.
let me know if I can be of further help,
kind regards