Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.6.0b10
Issue ID
888874
Regression
No
Collab - Deep Dive Start - Collab recovers poorly from latency spikes
Assuming you have a Collab enabled project. Assuming you have a Web Debugger of some kind that is capable of injecting latency into a network connection (in this case Clumsy was used - https://jagt.github.io/clumsy/download)(Fiddler also works well). Also assumed that your project is not empty.
1. On Clumsy, enable Lag Functions, click inbound and outbound and add a 300ms delay.
2. On Unity, click on Start Now
Notice that all transactions are quite delayed. Wait 10 seconds overall. Deactivate Clumsy. Notice that Collaborate does not immediately recover from the lag spike.
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
Add comment