Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
853897
Regression
No
NetworkConnection.SendWriter overrides previous messages when Server and Client runs on host instance
Reproduction steps:
1. Open attached project "NetworkSendWriter"
2. Open "Test" scene
3. Hit Play
Expected result:
Client receives 4 messages with values "1" and "2" ("From Server" messages in console)
Actual result:
Client receives 4 messages with value "2"
When Server and Client is on the same game instance (LAN Host) and Server sends message to the Client, all the messages are received together (Client RegisterHandler callback is not intercepting Server code) and that is where the issue occurs. However, when Client sends a message to the Server, Servers NetworkServer.RegisterHandler callback intercepts in code execution and handles the message. Therefore, the second message is also handled properly.
This doesn't occur on client launched on different game instance.
Reproduced on 5.2.5f1, 5.3.6p8, 5.4.0f3, 5.4.3f1, 5.5.0f1, 5.6.0a5
-
Mosinmotte2
Jun 16, 2019 10:12
Get a dedicated hosting server from siteground web hosting and run your website smoothly.
Source - http://www.webhostingreviewsx.co.uk/siteground-uk-hosting-reviews/
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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)