Search Issue Tracker
Fixed in 2018.1.X
Votes
1
Found in
2017.1.0f3
Issue ID
945346
Regression
No
Irrelevant warning message when using Animator.Play on a disabled object's animator
To reproduce:
1. Download and open attached "BugReport.zip" project.
2. Open "Scene" scene.
3. Enter Play mode.
4. Press A on keyboard to trigger animation.
5. Notice the console window.
Expected result: Console throws more descriptive warning. Since Animator does have a controller and it is only disabled, it should say that object with the animator is disabled or some other more descriptive information.
Actual result: Console throws irrelevant warning. It says that "Animator does not have an AnimatorController" when in fact it does have one, simply the object is disabled.
Reproduced with: 2017.3.0a7, 2017.2.0b10, 2017.1.1f1, 5.6.3p2, 5.5.4p4.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Add comment