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
- Incorrect ScrollToItem behavior when called on a deattached ListView
- Zooming in/out in Scene View window on the display the zoom takes place in does not work
- Changing Game View resolution when there are 2 Game View Windows on 2 different displays makes the view stretched
- Maximising Game view window on one display makes black bars appear on another display
- Creating a 3D Object when using 2 monitors and 2 Game View Windows on different monitors the created 3D Object only appears on one of them
Add comment