You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Joining the discord and screen sharing we were able to test when the race start countdown started for a player closer to the server and a player farther from it.
One player had the "GO" on screen while the other was still on "3", so what can be done is check for latency by pinging the clients and adjust the sending of start command times for each player with their latency offsets. That would be enough to sync the race start a bit (can't compensate local machine performance lag, of course).
The text was updated successfully, but these errors were encountered:
Joining the discord and screen sharing we were able to test when the race start countdown started for a player closer to the server and a player farther from it.
One player had the "GO" on screen while the other was still on "3", so what can be done is check for latency by pinging the clients and adjust the sending of start command times for each player with their latency offsets. That would be enough to sync the race start a bit (can't compensate local machine performance lag, of course).
The text was updated successfully, but these errors were encountered: