Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.2.0b10
Issue ID
946979
Regression
No
Changing generic animation to legacy while it is used in timeline throws "Assertion failed" error
How to reproduce:
1. Open the attached project
2. Open test scene and select Eskimo_2
3. If you open its timeline playable you can notice that it uses few animations
4. Find "people" character in the project
5. Change its rig to Legacy
6. Select Eskimo_2 in hierarchy
Actual result: you should get few "Assertion failed: Assertion failed on expression: 'MecanimDataWasBuilt()'" errors
Expected result: error should be clear and state that legacy animation clips are not supported on timeline. Just how it is written in inspector under animation after you select it in timeline
Reproducible: 2017.1.1f1, 2017.2.0b10, 2017.3.0a2, 2017.3.0a6
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
MistaGoustan
Sep 28, 2017 02:25
I am getting this error currently too. this is how I get it...
1) I get these two warnings:
The AnimationClip 'Idle' used by the Animation component 'Player' must be marked as Legacy.
Default clip could not be found in attached animations list.
2) I then make the changes it asks for and I get the:
Assertion failed: Assertion failed on expression: 'MecanimDataWasBuilt()'
The real problem is the warning: must be marked as legacy. which was a problem years ago but it seems to be one now as well.