Search Issue Tracker
Fixed in 5.4.0
Votes
1
Found in
5.3.1p4
Issue ID
765235
Regression
No
NetworkServer.GetConnectionStats are wrong with more than 1 client
Reproduction steps:(Gif below)
1) Open users submitted project and build it twice.
1.1) Alternatively you can run three copies of a project in three Editors.
2) Go into play mode in the editor and hit "LAN server Only(S)" UI button.
3) Run one of builds that you created or go into playmode in another Editor.
4) Click "LAN Client(C)" UI button. Then move around with the ball using arrow keys.
4.0) Collapse Console of Editor that runs server.
4.1) Notice NetworkServer.GetConnectionStats are printed.
4.2) Clear the console, you should see three collapsed logs piling up.
5) Repeat step 3 , 4, 4.1 and 4.2 with other Editor/Build.
Expected result: After your last input data should not be added up any more and clearing console should leave a few logs piling up.
Actual result: After your last input data keeps on being added - you can see that by a buildup of a new logs in the Console of the Editor that runs Server.
Note: Disconnecting one user brings things back to normal.
Reproduced with: 5.4.0b3, 5.3.2p1, 5.2.4f1, 5.1.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment