foriero लिखाThis one is project stopper.
You should not upgrade your projects to unsupported Unity versions. It's like going down a road which has been closed due to construction work just to find that there is a hole in the ground that you cannot get over now.
But anyway, we are happy to fix it so that we can officially support 2020.1 soon.
foriero लिखाI tried to look into it but have not found where you register the scriptable objects into the list!
You do know that you register them yourself at your SkeletonDataAsset by adding them to the list manually? They are not automatically added, they never were.
Nevertheless, the new problem with Unity 2020.1 occurs when re-importing the directory containing the asset: the list in the SkeletonDataAsset briefly contains no entries when they should be processed, after that the entries are de-serialized but then it's too late. This will be fixed in the mentioned ticket.
The issue documented in the ticket also turns out to have been false alarm. After adding a SkeletonDataModifierAsset to the list of a SkeletonDataAsset, you have to save the asset once, afterwards upon either a) modifying the json skeleton file or b) reimporting the parent directory, the SkeletonDataModifierAsset Apply() method is called correctly.
Just without saving, it behaved inconsistently, most of the time not applying the SkeletonDataModifierAsset. Closing the ticket now.
