New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Game stuck on ping > 300ms #2873
Comments
I have If I reset |
When I'm stuck, the game continue to render things (I see bots playing), but the input are dead. |
I still get the bug if I join with a 0.54.0 client. |
It looks like the bug occurs if The higher the ping is, the easier you get the bug with lower fps. The |
What is stuck is the input, the game renders properly and updates according to server state on every frame, we can see bots moving around and beacons moving on screen. |
The bug was already there in 0.54.0, I guess I only noticed it after 0.54.1 was released because we improved performance. |
I reproduce locally if I spawn a server listening on localhost and join with a client, and emulating a sudo tc qdisc add dev lo root netem delay 300ms With Edit: Setting Edit: To remove the emulated ping, one does:
|
Well, the command likely gives a |
I reproduce the bug with |
When the bug occurs, the game displays
|
The scoreboard displays the real ping (300ms in my example). |
I reproduce it on “Rakka Takka” server which is located in Australia.
When the ping is larger than 200ms, the game is stuck. I believe it's a bug, the game should lag a lot, but not be stuck.
The text was updated successfully, but these errors were encountered: