Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b1
Issue ID
900622
Regression
No
[UX] NetworkAnimator requires redundant reference to Animator
NetworkAnimator requires Animator Component to be present on GO, but also user has to manually add the Animator component to NetworkAnimator.
Regarding that there’s no option to add second Animator to object, this action looks a bit redundant and inconsistent
(e.g. with NetworkTransfrom, we don’t manually show which transform it needs to refer to).
To reproduce:
1. Create new GameObject.
2. Add NetworkAnimator component.
Note: Animator and NetworkIdentity components are auto-added.
Actual result: You're required to manually add Animator component reference to NetworkAnimator.
4. Optionally remove reference to Animator from NetworkAnimator:
Actual result:
```ResetParameterOptions
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)```
Expected result: Animator should be automatically linked to NetworkAnimator with no need to be explicitly added.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.