Search Issue Tracker
Won't Fix
Votes
4
Found in
2019.2.0a1
2019.2.0f1
2019.3.0a1
2020.1.0a1
Issue ID
1177585
Regression
No
[UNET] ping.DestroyPing does not work resulting in increasing ping delay
How to reproduce:
1. Open attached project "TrackerReg.zip" and scene "Main"
2. Enter Play mode
3. In Game view, click "refresh" button(Green button top-right corner)
4. Repeat step 3 a few times after refreshing is done (refresh is done when "247" in Console window is printed out)
5. Observe the time it takes to complete the refresh
Expected result: pinging takes the same amount of time between the refreshes. After each refresh click the ping.DestoryPing removes all the previous pinging
Actual result: pinging takes a lot more time after continues refresh button clicking
Reproducible with: 2019.2.2f1, 2019.3.0a12, 2020.1.0a1
Could not test with 2019.1 and older due to Canvas breaking and Package Manager errors
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
Add comment