Search Issue Tracker
Won't Fix
Votes
1
Found in
5.4.0f1
Issue ID
817487
Regression
No
[HLAPI] Starting connection that fails and then starting another that connects leads to delayed disconnection
Steps to reproduce:
1. Open attached "reproProject.zip"
2. run two instances
3. One instance should be launched as server
4. On second instance click "BadClient" and then "Connect"
5. wait for like 20seconds (might take up to 30
Actual: disconnects the client
Expected: client should not be disconnected from the connected server if his previous connection failed
note: repro video attached
Reproduced: 5.4.0f2, 5.3.0f4
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 RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
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)