Search Issue Tracker
Fixed
Votes
0
Found in [Package]
2.4.0
Issue ID
MTTB-1371
Regression
No
Two NetworkManager Player GameObjects are auto-spawned on Client when using NetworkSceneManager
Reproduction steps:
1. Open the attached “IN-103953.zip” project
2. Click the dropdown next to the Play mode button
3. Choose “Server + 1C” Play mode Scenario
4. Enter Play mode
5. Observe the Console in the newly opened (Client) Editor
Expected result: No warnings, only one NetworkManager Player is spawned
Actual result: “Tryingto spawn NetworkObjectId 6 that already exists!” warning is shown and two Players are spawned
Reproducible with: 1.12.0, 2.4.0 (6000.0.50f1, 6000.1.6f1, 6000.2.0b5)
Couldn’t test with: 2022.3.62f1 (Package not supported)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Also reproduces in builds running locally
- Also reported in discussions: https://discussions.unity.com/t/double-spawned-networkmanager-player-objects-when-using-networkscenemanager/1650791
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment