@Tirex @SnowyMano @AKSRT @beerslayer I can't seem to replicate the issue but there is clearly something going on so I tried to change the target framework to 4.5.
Do you mind downloading the RC
here and come back to me with results before I push this release?
If this doesn't work I will have to take a deeper looks in to it during the weekend when I have more time.
37345: Receives driver stint reset for car 1001
37345: startingTime is not set?
37345: Updated 0 clients with new carSystem for car 1001 (0l)
37391: Updated 0 clients with new carSystem for car 1001 (16l)
38323: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 38329 (now: 38323 offset: 36984)
39077: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 39083 (now: 39077 offset: 36983)
40319: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 40325 (now: 40319 offset: 36983)
40426: ==ERR: onCarUpdate (1001): timestamp is 6 ms in the future: 40433 (now: 40426 offset: 36983)
40697: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 40703 (now: 40697 offset: 36983)
40804: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 40810 (now: 40804 offset: 36983)
41291: ==ERR: onCarUpdate (1001): timestamp is 7 ms in the future: 41299 (now: 41291 offset: 36984)
41506: ==ERR: onCarUpdate (1001): timestamp is 7 ms in the future: 41514 (now: 41506 offset: 36984)
41777: ==ERR: onCarUpdate (1001): timestamp is 6 ms in the future: 41784 (now: 41777 offset: 36984)
41995: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 42001 (now: 41995 offset: 36984)
43019: ==ERR: onCarUpdate (1001): timestamp is 5 ms in the future: 43025 (now: 43019 offset: 36983)
47345: Late lastUdpPaketReceived for connId 1: 2367 ms (Alexandr Frol)
And such a message is issued endlessly, because of what is it?