mirror of
https://github.com/genxium/DelayNoMore
synced 2024-12-26 03:39:00 +00:00
12 lines
901 B
Markdown
12 lines
901 B
Markdown
|
Under the current "input delay" algorithm, the lag of a single player would cause all the other players to receive outdated commands, e.g. when at a certain moment
|
||
|
|
- player#1: renderFrameId = 100, significantly lagged due to local CPU being overheated
|
||
|
|
- player#2: renderFrameId = 240
|
||
|
|
- player#3: renderFrameId = 239
|
||
|
|
- player#4: renderFrameId = 242
|
||
|
|
|
||
|
|
players #2, #3 #4 would receive "outdated(in their subjective feelings)" from then on, and be forced to rollback many frames.
|
||
|
|
|
||
|
|
In a "no-server & p2p" setup, I couldn't think of a proper way to cope with such edge case. On the frontend we could only mitigate the impact to players #2, #3, #4 by certain buffering mechanisms.
|
||
|
|
|
||
|
|
However in a "server as authority" setup, the server could force confirming an inputFrame without player#1's upsync, and notify player#1 to apply a "roomDownsyncFrame" as well as drop all its outdated local inputFrames.
|