What's new

Constant Desync problems.

Status
Not open for further replies.

SireElite

Bronze Member
Joined
Oct 16, 2016
Messages
159
Hey,

For some reason I constantly get desynced ingame on RCRP, I'm unsure if it happens to other games though, this seems to be a problem with SA-MP in particular.
Before anyone says "ISP", It surely can't be that, as I can host lobbies in other games fine, so It can't be a problem with my net.

I had a problem however, where I had extreme packet-loss and high ping, but I fixed that not so long ago, yet I still suffer issues in SA-MP, but not as much as before.

Ingame, my ping is fine and my packet loss is usually 0.0, and can sometimes go up to 0.4 or 0.5

I did many solutions and whatnot online, and scanned my PC for malware and viruses on a daily basis.

I did a diagnostics test though, heres the result.

Code:
Running RC-RP Diagnostics test... 
Retrieving system date and time. 
22/12/2017 
21:22
 
------- Ping/Traceroute to EU.FROSTGAMING.COM -------: 

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Reply from 185.198.188.98: bytes=32 time=23ms TTL=52
Reply from 185.198.188.98: bytes=32 time=62ms TTL=52
Reply from 185.198.188.98: bytes=32 time=27ms TTL=52
Reply from 185.198.188.98: bytes=32 time=20ms TTL=52
Reply from 185.198.188.98: bytes=32 time=54ms TTL=52
Reply from 185.198.188.98: bytes=32 time=26ms TTL=52
Reply from 185.198.188.98: bytes=32 time=24ms TTL=52
Reply from 185.198.188.98: bytes=32 time=23ms TTL=52

Ping statistics for 185.198.188.98:
    Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 62ms, Average = 32ms

Tracing route to eu.frostgaming.com [185.198.188.98]
over a maximum of 30 hops:

  1     5 ms     3 ms     3 ms  192.168.0.1 
  2    16 ms    21 ms    17 ms  10.216.68.1 
  3    31 ms    20 ms    19 ms  leed-core-2b-xe-133-0.network.virginmedia.net [62.252.232.241] 
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    31 ms    36 ms    21 ms  manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242] 
  7    40 ms    24 ms    26 ms  86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86] 
  8     *        *        *     Request timed out.
  9    30 ms    28 ms    30 ms  uk-lon03a-ri1-ae2-0.aorta.net [84.116.135.46] 
 10    58 ms    30 ms    36 ms  213.46.174.38 
 11    26 ms    24 ms    22 ms  185.198.188.0 
 12   445 ms    50 ms    40 ms  185.198.188.1 
 13   143 ms    62 ms   198 ms  185.198.188.3 
 14    30 ms    30 ms    50 ms  rev.srv3.eu.frostgaming.com [185.198.188.98] 

Trace complete.
 
------- Ping/Traceroute to SERVER.REDCOUNTYRP.COM -------: 

Pinging server.redcountyrp.com [185.198.188.100] with 32 bytes of data:
Reply from 185.198.188.100: bytes=32 time=32ms TTL=52
Reply from 185.198.188.100: bytes=32 time=30ms TTL=52
Reply from 185.198.188.100: bytes=32 time=36ms TTL=52
Reply from 185.198.188.100: bytes=32 time=28ms TTL=52
Reply from 185.198.188.100: bytes=32 time=37ms TTL=52
Reply from 185.198.188.100: bytes=32 time=54ms TTL=52
Reply from 185.198.188.100: bytes=32 time=63ms TTL=52
Reply from 185.198.188.100: bytes=32 time=23ms TTL=52

Ping statistics for 185.198.188.100:
    Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 63ms, Average = 37ms

Tracing route to server.redcountyrp.com [185.198.188.100]
over a maximum of 30 hops:

  1     6 ms    11 ms    19 ms  192.168.0.1 
  2   198 ms     *      148 ms  10.216.68.1 
  3    30 ms    24 ms    34 ms  leed-core-2b-xe-003-0.network.virginmedia.net [62.252.232.237] 
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    24 ms    20 ms    48 ms  manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242] 
  7    28 ms    22 ms    26 ms  86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86] 
  8     *        *        *     Request timed out.
  9    24 ms    29 ms    23 ms  uk-lon03a-ri1-ae2-0.aorta.net [84.116.135.46] 
 10    21 ms    26 ms    22 ms  213.46.174.38 
 11    36 ms    34 ms    31 ms  185.198.188.0 
 12    44 ms    24 ms    49 ms  185.198.188.1 
 13    30 ms    33 ms    27 ms  185.198.188.3 
 14    27 ms    26 ms    24 ms  rev.srv5.eu.frostgaming.com [185.198.188.100] 

Trace complete.
 
------- Ping/Traceroute to GOOGLE.COM -------: 

Pinging google.com [216.58.204.14] with 32 bytes of data:
Reply from 216.58.204.14: bytes=32 time=41ms TTL=55
Reply from 216.58.204.14: bytes=32 time=26ms TTL=55
Reply from 216.58.204.14: bytes=32 time=43ms TTL=55
Reply from 216.58.204.14: bytes=32 time=144ms TTL=55

Ping statistics for 216.58.204.14:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 26ms, Maximum = 144ms, Average = 63ms

Tracing route to google.com [216.58.204.14]
over a maximum of 30 hops:

  1     5 ms    10 ms     4 ms  192.168.0.1 
  2     *       63 ms    28 ms  10.216.68.1 
  3    25 ms    21 ms    22 ms  leed-core-2a-xe-133-0.network.virginmedia.net [62.252.232.97] 
  4     *        *        *     Request timed out.
  5    24 ms    22 ms    30 ms  tcl5-ic-4-ae5-0.network.virginmedia.net [62.252.192.246] 
  6    32 ms    39 ms    22 ms  246-14-250-212.static.virginm.net [212.250.14.246] 
  7    52 ms   189 ms    23 ms  108.170.246.193 
  8    56 ms    94 ms   173 ms  108.170.238.145 
  9     *      297 ms   129 ms  lhr35s07-in-f14.1e100.net [216.58.204.14] 

Trace complete.
 

Max Bluman

Donator
Joined
Apr 1, 2016
Messages
282
In this instance I believe you are experiencing the bug with the VirginMedia SuperHub 3 instead of your ISP itself. It's a known bug in relation to the router CPU not being able to keep up with VM speeds causing latency lag. Could you confirm what VM plan you are on as your tracert shows a business hop and also what hub you have?
 

SireElite

Bronze Member
Joined
Oct 16, 2016
Messages
159
I got a VirginMedia Superhub 3, and I don't know what plan I've purchased lol, since my parents are the one whom are paying for the household broadband.
 

fr0st

SysAdmin
System Administrator
Joined
Jan 28, 2011
Messages
444
Location
Texas
Can you re-run the test while the problem is occuring? Alt-tab and immediately run the tool and provide me the result.
 

SireElite

Bronze Member
Joined
Oct 16, 2016
Messages
159
Yeah, the thing is it occurs randomly, sometimes its absolutely fine on RCRP and other games, then it might just die on me for a bit.
I'll reply when the problem occurs.
 

SireElite

Bronze Member
Joined
Oct 16, 2016
Messages
159
fr0st said:
Can you re-run the test while the problem is occuring? Alt-tab and immediately run the tool and provide me the result.
Running RC-RP Diagnostics test...
Retrieving system date and time.
29/12/2017
00:00

------- Ping/Traceroute to EU.FROSTGAMING.COM -------:

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Reply from 185.198.188.98: bytes=32 time=30ms TTL=52
Reply from 185.198.188.98: bytes=32 time=26ms TTL=52
Reply from 185.198.188.98: bytes=32 time=69ms TTL=52
Reply from 185.198.188.98: bytes=32 time=23ms TTL=52
Reply from 185.198.188.98: bytes=32 time=40ms TTL=52
Reply from 185.198.188.98: bytes=32 time=39ms TTL=52
Reply from 185.198.188.98: bytes=32 time=30ms TTL=52
Reply from 185.198.188.98: bytes=32 time=40ms TTL=52

Ping statistics for 185.198.188.98:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 69ms, Average = 37ms

Tracing route to eu.frostgaming.com [185.198.188.98]
over a maximum of 30 hops:

1 9 ms 3 ms 4 ms 192.168.0.1
2 15 ms 17 ms 16 ms 10.216.68.1
3 952 ms 87 ms 33 ms leed-core-2b-xe-133-0.network.virginmedia.net [62.252.232.241]
4 * * * Request timed out.
5 * * * Request timed out.
6 95 ms 15 ms 13 ms manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242]
7 30 ms 25 ms 26 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
8 * * * Request timed out.
9 27 ms 32 ms 29 ms uk-lon03a-ri1-ae2-0.aorta.net [84.116.135.46]
10 26 ms 20 ms 27 ms 213.46.174.38
11 26 ms 27 ms 23 ms 185.198.188.0
12 58 ms 43 ms 117 ms 185.198.188.1
13 26 ms 22 ms 27 ms 185.198.188.3
14 31 ms 26 ms 22 ms rev.srv3.eu.frostgaming.com [185.198.188.98]

Trace complete.

------- Ping/Traceroute to SERVER.REDCOUNTYRP.COM -------:

Pinging server.redcountyrp.com [185.198.188.100] with 32 bytes of data:
Reply from 185.198.188.100: bytes=32 time=23ms TTL=52
Reply from 185.198.188.100: bytes=32 time=22ms TTL=52
Reply from 185.198.188.100: bytes=32 time=21ms TTL=52
Reply from 185.198.188.100: bytes=32 time=30ms TTL=52
Reply from 185.198.188.100: bytes=32 time=23ms TTL=52
Reply from 185.198.188.100: bytes=32 time=207ms TTL=52
Reply from 185.198.188.100: bytes=32 time=30ms TTL=52
Reply from 185.198.188.100: bytes=32 time=36ms TTL=52

Ping statistics for 185.198.188.100:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 207ms, Average = 49ms

Tracing route to server.redcountyrp.com [185.198.188.100]
over a maximum of 30 hops:

1 13 ms 7 ms 9 ms 192.168.0.1
2 16 ms 17 ms 17 ms 10.216.68.1
3 18 ms 22 ms 17 ms leed-core-2b-xe-003-0.network.virginmedia.net [62.252.232.237]
4 * * * Request timed out.
5 * * * Request timed out.
6 29 ms 24 ms 19 ms manc-ic-1-ae1-0.network.virginmedia.net [62.254.42.242]
7 31 ms 23 ms 26 ms 86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
8 * * * Request timed out.
9 29 ms 21 ms 42 ms uk-lon03a-ri1-ae2-0.aorta.net [84.116.135.46]
10 47 ms 29 ms 32 ms 213.46.174.38
11 33 ms 24 ms 35 ms 185.198.188.0
12 94 ms 59 ms 46 ms 185.198.188.1
13 31 ms 33 ms 29 ms 185.198.188.3
14 102 ms 39 ms 41 ms rev.srv5.eu.frostgaming.com [185.198.188.100]

Trace complete.

------- Ping/Traceroute to GOOGLE.COM -------:

Pinging google.com [216.58.204.14] with 32 bytes of data:
Reply from 216.58.204.14: bytes=32 time=28ms TTL=55
Reply from 216.58.204.14: bytes=32 time=30ms TTL=55
Reply from 216.58.204.14: bytes=32 time=23ms TTL=55
Reply from 216.58.204.14: bytes=32 time=25ms TTL=55

Ping statistics for 216.58.204.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 30ms, Average = 26ms

Tracing route to google.com [216.58.204.14]
over a maximum of 30 hops:

1 9 ms 6 ms 4 ms 192.168.0.1
2 30 ms 16 ms 19 ms 10.216.68.1
3 18 ms 21 ms 21 ms leed-core-2a-xe-133-0.network.virginmedia.net [62.252.232.97]
4 * * * Request timed out.
5 23 ms 26 ms 31 ms tcl5-ic-4-ae5-0.network.virginmedia.net [62.252.192.246]
6 19 ms 24 ms 30 ms 246-14-250-212.static.virginm.net [212.250.14.246]
7 23 ms 27 ms 32 ms 108.170.246.193
8 40 ms 20 ms 24 ms 108.170.238.145
9 28 ms 29 ms 29 ms lhr35s07-in-f14.1e100.net [216.58.204.14]

Trace complete.
THIS might be done when the crash occured on the server earlier today, can't remember.
 

fr0st

SysAdmin
System Administrator
Joined
Jan 28, 2011
Messages
444
Location
Texas
We made some changes recently that might help with packet loss. Has this happened anymore after the 11th? (yesterday)
 
Status
Not open for further replies.
Top