-
Notifications
You must be signed in to change notification settings - Fork 47
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
Lightyear breaks down if the fps becomes too low? #593
Comments
Is this related to a specific platform / transport? |
It was on web, with webtransport. |
Would be nice to test if this happens on other platforms/transports too otherwise it might be an issue with xwt / lightyears integration of it |
I'd guess it's not specific to xwt because everything is solid under normal circumstances. It's only when the FPS is too slow, and updates begin to pile up quicker than they're being processed. It's like a weird death spiral. My game runs at 10fps when the console is up and printing logs, or 30-40fps in debug mode without the console. Opening the console was just a convenient way to reproduce a low fps. The rollbacks don't make much sense to me, or I'm misunderstanding how they work. I believed the default redundancy of packets is 10, meaning as long as you don't drop 10+ packets in a row, you should never see a rollback. I am buffering inputs every update, e.g. the framerate. My input send rate is 10Hz. With a packet redundancy of 10, I wouldn't expect a rollback to happen unless the latency is at least 1 full second (0.10s * 10 packets). My input is fully deterministic as well. Instead, it's constant rollbacks when the FPS is low, (<20fps). |
Example raised by simbleau.
Symptoms:
TODO:
The text was updated successfully, but these errors were encountered: