Search Issue Tracker
By Design
Votes
0
Found in
5.6.2f1
Issue ID
941575
Regression
No
NetworkTransport.GetRemoteDelayTimeMS returns 0 via Server to Client message
How to reproduce:
1. Open the attached project
2. Simulate network latency (tested with Clumsy)
2. Build & Run the project
3. In the built project select "Lan Server Only(S)"
4. In the Editor enter Play mode
5. Select "Lan Client(C)"
Actual result: NetworkTransport.GetRemoteDelayTimeMS returns 0 in the console.
Expected result: NetworkTransport.GetRemoteDelayTimeMS should return the delay time.
Reproduced with: 2017.3.0a4, 2017.2.0b6, 2017.1.0p3, 5.6.3f1, 5.5.4p2.
Note: Rarely, the delay is correct.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2018.1.X):
This is working as per Design