Search Issue Tracker
Won't Fix
Votes
1
Found in
5.6.1f1
Issue ID
914690
Regression
Yes
The client's player object is not destroyed on the host immediately after it disconnected
To reproduce:
1. Open the project, attached by tester (timeoutBug.zip)
2. Build the project for standalone
3. Launch the game in the editor as host
4. Launch the build as client
5. Click Stop button in client
6. Repeat 4 - 6
7. Observe the Hierarchy in the Editor
Expected: the client's player object is destroyed immediately and no errors are shown
Actual: the client's player object doesn't get destroyed in the host as soon as the client disconnects
Reproduced in 5.6.0b11, 5.6.1f1, 2017.1.0b7, 2017.2.0a1
Did not reproduced in 5.5.3p2, 5.6.0b10
Regression introduced in 5.6.0b11
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
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
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.