Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.19f1
2018.3.0f1
2018.3.0f2
2019.1.0a11
Issue ID
1119461
Regression
Yes
Deserialization doesn't work on Unreliable Channels, while a Reliable Channel is present on Client
Reproduction steps:
1. Open two instances of "NetworkIssue.zip" project
2. Enter Play mode
3. In one instance press "LAN Host(H)", in the other press "LAN Client(C)"
4. See Console output on Client
Expected Result: Both "NetScriptA" and "NetScriptB" are deserialized
Actual Result: "NetScriptB" is not deserialized because it's on an unreliable channel
Reproduced with: 2019.1.0a11, 2018.3.3f1, 2018.2.20f1
Did not reproduce on: 2019.2.0a2, 2019.1.0b1, 2019.2.0a12, 2019.1.0a10, 2019.1.0a7, 2019.1.0a5, 2019.1.0a1, 2018.3.0b12, 2018.3.0b10, 2018.3.0b5, 2018.3.0a1, 2018.2.18f1, 2018.2.15f1, 2018.2.10f1, 2018.2.0f1, 2018.2.0b1, 2018.2.0a1, 2018.1.9f2, 2017.4.19f1, 2017.3.0a1
Note:
"NetworkBehaviour" is deprecated from 2019.1.0a12 and up
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
This is a duplicate of issue #1110031