Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Won't Fix in 2017.1.X
Votes
1
Found in
2017.1.1p2
Issue ID
956316
Regression
No
Unity crashes at PlayableOutputHandle_CUSTOM_INTERNAL_CALL_SetSourcePlayableInternal when entering the play mode
This crash happens when using AnimationMixerPlayable as the source for the AnimationPlayableOutput but AnimationMixerPlayable in not initialized.
To reproduce:
1. Open project attached by the user
2. Open scene "Scene"
3. Enter the play mode
Expected result: Unity shouldn't allow entering play mode as AnimationMixerPlayable is not initialized. It should throw exceptions.
Actual result: Unity crashes
Reproduced with: 2017.1.1p3, 2017.2.0f2, 2017.3.0b3
User's code uses C# 4.0 features so wasn't able to test on earlier versions
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
Add comment