Search Issue Tracker

Fixed in 2019.2

Fixed in 2018.4

Planned for 2019.1

Votes

0

Found in

2017.4.0f1

2018.2.15f1

Issue ID

1100643

Regression

No

MecanimDataWasBuilt() Error when calling playableOutput.SetSourcePlayable()

Animation

-

Steps to reproduce:
1. Open User-supplied project
2. Play the Scene

Expected: no error
Actual: "Assertion failed: Assertion failed on expression: 'MecanimDataWasBuilt()" appears in the Console window

Reproduced in: 2017.4.0f1, 2017.4.16f1, 2018.3.0f1, 2019.1.0a12

Full Stack:
Assertion failed: Assertion failed on expression: 'MecanimDataWasBuilt()'
0x00000001412F26E6 (Unity) StackWalker::GetCurrentCallstack
0x00000001412F328F (Unity) StackWalker::ShowCallstack
0x00000001411B1BE0 (Unity) GetStacktrace
0x00000001406DB5F3 (Unity) DebugStringToFile
0x00000001406DBDD1 (Unity) DebugStringToFile
0x00000001416983B7 (Unity) AnimationClip::GetRuntimeAsset
0x00000001416FB765 (Unity) UnityEngine::Animation::CreateAnimationSetBindings
0x000000014171A4B8 (Unity) Animator::CreateBindings
0x000000014171DAA6 (Unity) Animator::CreateObject
0x000000014171F3F1 (Unity) Animator::Prepare
0x000000014172114C (Unity) Animator::UpdateAvatars
0x00000001404EDC90 (Unity) DirectorManager::ExecuteProcessCallbacks
0x00000001404F64BE (Unity) `DirectorManager::InitializeClass'::`10'::PreLateUpdateDirectorUpdateAnimationBeginRegistrator::Forward
0x000000014071DAB0 (Unity) PlayerLoop
0x00000001411DEC65 (Unity) PlayerLoopController::UpdateScene
0x00000001411E902A (Unity) PlayerLoopController::EnterPlayMode
0x00000001411E98A6 (Unity) PlayerLoopController::SetIsPlaying
0x00000001411EA6F6 (Unity) Application::TickTimer
0x00000001414101DF (Unity) MainMessageLoop
0x0000000141411A9C (Unity) WinMain
0x0000000141E662B8 (Unity) __tmainCRTStartup
0x00007FFF63EA3034 (KERNEL32) BaseThreadInitThunk
0x00007FFF66263691 (ntdll) RtlUserThreadStart

  1. Response avatar

    Resolution Note (fix version 2019.2):

    Users is using a legacy animation clip with playables which is not supported.

    AnimationClipPlayable will now throw an ArgumentException when a legacy clip is used.

    To fix the issue, simply change 

    var clip = new AnimationClip {name = name, legacy = true, frameRate = frameRate};

    to

    var clip = new AnimationClip {name = name, legacy = false, frameRate = frameRate};

    Fixed in: 2018.4.4f1, 2019.2.0a9

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.