Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0f2
Issue ID
1036144
Regression
No
"Event EventCrouch called on client" error pops up when two classes implement same Interface and one of them is NetworkBehaviour
How to reproduce:
1. Open attached Unity project "NetworkInterfaceTest"
2. Load scene "SampleScene"
3. Enter the Play mode
4. Press "Crouch"
Expected result: Error shouldn't pop up because Networking is not used.
Actual result: "Event EventCrouch called on client" error pops up.
Reproduced with: 2018.2.0b7, 2018.1.4f1, 2017.4.5f1, 2017.2.3p1, 2017.1.4f1.
Note: NetworkBehavior class is not used in a scene.
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
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 on this one.
For more information and next steps see this [blog post](https://blogs.unity3d.com/2018/08/02/evolving-multiplayer-games-beyond-unet/) and the [FAQ](https://support.unity3d.com/hc/en-us/articles/360001252086-UNet-Deprecation-FAQ)