Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.3p4
Issue ID
863214
Regression
Yes
Using CinemaDirector, because of Mecanim Track, Unity crashes in mecanim::statemachine::StartState
Reproduction steps:
1. Open the attached project;
2. Open the scene "1";
3. Press Ctrl + Shift + D (CinemaDirector will open);
4. Click Play button in the CinemaDirector window;
Actual result: Unity crashes in mecanim::statemachine::StartState (in about 12 second).
Expected result: Unity shouldn't crash.
Note: I find out that the crash is caused by Mecanim Track Animators Transition Duration and the blue line which represents animation end (blue_line.jpg). When Animators Transition Duration is not enough until it reaches the blue line, Unity crashes. Also, if the blue line is set to time before Animators finish their duration, it also causes the crash.
Furthermore, Unity doesn't crash, if after click Play button in the CinemaDirector window, Unity loses the focus (turn on the other program or a browser).
Reproduced with: 5.4.0a2, 5.4.2f2, 5.5.0f3, 5.6.0b3.
Not reproducible: 5.2.5f1, 5.3.6p4
Regression introduced in 5.4.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Add comment