Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.9f1
Issue ID
1069907
Regression
No
"NetworkManager.StopClient()" results in confusing "ServerDisconnected due to error: Timeout" errors
Reproduction steps:
1. Open "MinimalRepro" project
2. Build the Player with "Development Build" enabled
3. Launch two instances of the Player (One for the Server, one for the Client)
4. In one instance (Left) click on "Server Start"
5. In the other instance (Right) click on "Client Start"
6. Press "1" on your keyboard
7. Repeat step 5-6 for 4-5 times
8. Notice "ServerDisconnected" Errors in the "Development Console" (Left)
Expected Result: The log specifies which Client disconnected with the "ServerDisconnected" error
Actual Result: The log isn't specific with which Client disconnected
Reproduced with: 2018.3.0a8, 2018.2.4f1, 2018.1.9f1, 2017.4.9f1, 2017.3.2f1, 2017.2.3p3, 2017.1.5f1
Comments (1)
-
kpro1999
Mar 12, 2019 11:03
why not fix!!!
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
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)