Search Issue Tracker
Fixed in 5.2.1
Votes
0
Found in
5.2.1f1
Issue ID
729924
Regression
No
Animator window does not show Animator Controller state machine after stopping the scene when using Runtime Animator Controller
Steps to reproduce:
1. Open the attached project
2. Open 'Main' scene
3. Double-click 'Run Controller' asset to open in in an Animator window
4. Play the scene
5. Select 'veteran' game object
6. Stop the scene
7. Notice Animator Window is emptied and does not show the previously opened 'Run Cocntroller'. Try to open any other animator controller after that, notice it does not work.
Notes: Does not occur if the animator controller is simply attached to the animator component on the game object (instead of using runtime animator controller). Can be workarounded by closing and reopening the Animator window.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
Add comment