Search Issue Tracker

Won't Fix

Votes

0

Found in

2017.1.0f1

Issue ID

927984

Regression

No

NetworkLobbyManager duplicates elements in hierarchy after a failed call to StartClient()

Networking

-

This case has two examples on how to reproduce the issue. There are two scenes ("Lobby" and "Lobby2") within the attached project, both showcasing the bug.

Reproduction Steps:
Lobby:
1. Enter Play mode.
2. In Game, select "Guest".
3. Select "Play as Guest".
4. Wait until error "ClientDisconneted due to error: Timeout" appears in the console.

Expected result: Only one NetworkManager remains in the main scene hierarchy.
Actual result: Two Network Managers appear within the scene, one in the main "Lobby" scene and one in "DontDestroyOnLoad". If one is disabled, a duplicate remains.

Lobby2:
1. Enter Play mode.
2. Select "Join".
3. Wait until error "ClientDisconneted due to error: Timeout" appears in the console.

Expected result: Only one LobbyManager remains in the scene.
Actual result: There are two LobbyManagers in "DontDestroyOnLoad".

Reproducible with: 5.5.4f1, 5.6.1p3, 2017.1.0f2, 2017.2.0b1

  1. 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)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.