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
- Red spots appear when Blending Lighting Scenarios using Adaptive Probe Volumes
- [Windows] About Unity Window needs to be opened twice to adapt to resolution
- NullReferenceException and temporary graph corruption after entering playmode if output node connection was changed
- Sprite Renderer with Animation does not reflect Sprite changes in the Scene when switching Mask Interaction
- Error "NullReferenceException: Object reference not set to an instance of an object" is present when loading 3D text mesh in Player from an asset bundle that is built with an older Editor version
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.