13-03-2020, 03:21 PM
(This post was last modified: 13-03-2020, 03:33 PM by josemendez.)
(13-03-2020, 01:37 PM)fiasko Wrote: Alright, understood. But how should we go about this so that this bug is addressed? Should I file a bug report, also sending "Tearable cable.asset" although this part of your paid asset? Am I allowed to do so? Would you rather do that, being able to better explain what's behind this?
Hi,
Tearable cable.asset is probably not the culprit. Any blueprint asset in Obi (including, but not limited to Tearable cable) contains constraints, and Unity can become confused if it tries to serialize them (when obviously it shouldn't, according to its own documentation: https://docs.unity3d.com/Manual/script-S...ation.html)
Quote:To use field serialization you must ensure it:
Is public, or has a SerializeField attribute
Is not static
Is not const
Is not readonly
Has a fieldtype that can be serialized. (See Simple field types that can be serialized, below.)
This particular field is protected and its type cannot be serialized, so it fails two of the conditions for serialization. I will create a post in their forums explaining the issue. Thanks for reporting this!
Edit: Here's the post in the forums. Will stay tuned to it:
https://forum.unity.com/threads/serializ...b1.846049/