What's new

High PL, getting stuck over and over at the character selection screen.

Status
Not open for further replies.

Dopehead

Bronze Member
Joined
Sep 6, 2017
Messages
445
Greetings,

Since the migration, my PL had dropped drastically from 1 - 3 (usually) to 0 - 0.9 but since yesterday, I've been facing problems with the server, the PL has once again swarmed, now I'm getting 15 PL and even in the dry hours (when there are less than 30 players). I've no idea what to do, once I input my password, I get stuck in the character selection menu. I'm facing this problem only on Red County otherwise I play on a deathmatch server and I get 0 packetloss. I'll attach a diagnostic test with it, if it is needed.

I'm in an official faction and it's very important to update the media regularly, hence I'd be very much thankful if this could be solved as soon as possible.

Thanks,
Dope-head
 

Curtis

Banned
Joined
Jun 13, 2017
Messages
923
When I had this problem I just had to wait it out. There's not much you can do, I'm afraid.
 

Dopehead

Bronze Member
Joined
Sep 6, 2017
Messages
445
Curtis said:
When I had this problem I just had to wait it out. There's not much you can do, I'm afraid.
For how long this problem went on?
 

Curtis

Banned
Joined
Jun 13, 2017
Messages
923
Dopehead said:
Curtis said:
When I had this problem I just had to wait it out. There's not much you can do, I'm afraid.
For how long this problem went on?
For me it was only around the peak times so I just waited til less people were online.
 

Dopehead

Bronze Member
Joined
Sep 6, 2017
Messages
445
Thing is, it actually happens when there are very less players, can it be a problem with my ISP?
 

Curtis

Banned
Joined
Jun 13, 2017
Messages
923
Dopehead said:
Thing is, it actually happens when there are very less players, can it be a problem with my ISP?
It could be.

Are you doing anything else whilst playing SA:MP? E.G. streaming / downloading any content?
 

Dopehead

Bronze Member
Joined
Sep 6, 2017
Messages
445
Curtis said:
Dopehead said:
Thing is, it actually happens when there are very less players, can it be a problem with my ISP?
It could be.

Are you doing anything else whilst playing SA:MP? E.G. streaming / downloading any content?
No, I'm not.
 

Dopehead

Bronze Member
Joined
Sep 6, 2017
Messages
445
Giga said:
Hello,

Please do attach the results of your diagnostics test so we can figure out what is causing the hiccup.
Code:
Running RC-RP Diagnostics test... 
Retrieving system date and time. 
Sun 11/12/2017 
05:15 PM
 
------- Ping/Traceroute to EU.FROSTGAMING.COM -------: 

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Request timed out.
Reply from 185.198.188.98: bytes=32 time=695ms TTL=46
Request timed out.
Reply from 185.198.188.98: bytes=32 time=686ms TTL=46
Reply from 185.198.188.98: bytes=32 time=758ms TTL=46
Request timed out.
Reply from 185.198.188.98: bytes=32 time=168ms TTL=46
Reply from 185.198.188.98: bytes=32 time=179ms TTL=46

Ping statistics for 185.198.188.98:
    Packets: Sent = 8, Received = 5, Lost = 3 (37% loss),
Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 758ms, Average = 497ms

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

  1     1 ms     3 ms     2 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3     4 ms     7 ms     3 ms  192.168.101.1 
  4     6 ms    81 ms    72 ms  103-86-55-1.optix.pk [103.86.55.1] 
  5     5 ms     9 ms    10 ms  202.141.224.69 
  6     7 ms     6 ms     6 ms  tw136-static192.tw1.com [119.63.136.192] 
  7     7 ms     5 ms     5 ms  110.93.253.197 
  8   185 ms   132 ms   134 ms  134.0.220.118 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11   251 ms   306 ms   141 ms  134.0.219.17 
 12   260 ms   147 ms   159 ms  v217.core1.ams1.he.net [216.66.80.213] 
 13   153 ms   161 ms   151 ms  100ge9-1.core1.lon2.he.net [72.52.92.213] 
 14     *        *        *     Request timed out.
 15   182 ms     *        *     185.198.188.1 
 16   153 ms   195 ms   172 ms  185.198.188.3 
 17     *      153 ms   165 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:
Request timed out.
Reply from 185.198.188.100: bytes=32 time=172ms TTL=46
Reply from 185.198.188.100: bytes=32 time=152ms TTL=46
Reply from 185.198.188.100: bytes=32 time=152ms TTL=46
Reply from 185.198.188.100: bytes=32 time=151ms TTL=46
Request timed out.
Reply from 185.198.188.100: bytes=32 time=176ms TTL=46
Reply from 185.198.188.100: bytes=32 time=151ms TTL=46

Ping statistics for 185.198.188.100:
    Packets: Sent = 8, Received = 6, Lost = 2 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 151ms, Maximum = 176ms, Average = 159ms

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

  1     1 ms     1 ms     1 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3    21 ms    41 ms     6 ms  192.168.102.1 
  4   151 ms   162 ms   164 ms  103-86-52-1.optix.pk [103.86.52.1] 
  5   185 ms   181 ms   207 ms  202.141.224.69 
  6    57 ms    54 ms    55 ms  tw136-static192.tw1.com [119.63.136.192] 
  7    16 ms    13 ms    14 ms  110.93.253.197 
  8   152 ms   157 ms   139 ms  134.0.220.118 
  9     *        *        *     Request timed out.
 10   139 ms   162 ms   140 ms  82.178.32.181 
 11   454 ms   419 ms  1112 ms  v217.core1.ams1.he.net [216.66.80.213] 
 12   712 ms   321 ms   327 ms  100ge9-1.core1.lon2.he.net [72.52.92.213] 
 13     *        *        *     Request timed out.
 14     *      394 ms   354 ms  185.198.188.1 
 15   308 ms     *        *     185.198.188.3 
 16   402 ms   729 ms   612 ms  rev.srv5.eu.frostgaming.com [185.198.188.100] 

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

Pinging google.com [74.125.200.102] with 32 bytes of data:
Reply from 74.125.200.102: bytes=32 time=1066ms TTL=39
Reply from 74.125.200.102: bytes=32 time=998ms TTL=39
Reply from 74.125.200.102: bytes=32 time=1165ms TTL=39
Reply from 74.125.200.102: bytes=32 time=1220ms TTL=39

Ping statistics for 74.125.200.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 998ms, Maximum = 1220ms, Average = 1112ms

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

  1     6 ms     2 ms     1 ms  192.168.0.1 
  2     *        *        *     Request timed out.
  3     3 ms     6 ms     2 ms  192.168.102.1 
  4    94 ms   102 ms   102 ms  103-86-52-1.optix.pk [103.86.52.1] 
  5     9 ms    10 ms     6 ms  202.141.224.69 
  6     7 ms     6 ms     6 ms  tw136-static192.tw1.com [119.63.136.192] 
  7     6 ms     5 ms     7 ms  110.93.253.197 
  8   153 ms   141 ms   140 ms  134.0.220.118 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11   836 ms   426 ms   151 ms  134.0.217.86 
 12     *        *      222 ms  82.178.32.194 
 13   159 ms   198 ms   308 ms  108.170.241.172 
 14   164 ms   190 ms   164 ms  216.239.42.213 
 15   164 ms     *      295 ms  209.85.245.231 
 16   264 ms   265 ms   264 ms  72.14.235.117 
 17   317 ms   304 ms   303 ms  209.85.252.46 
 18   315 ms   329 ms   327 ms  72.14.233.111 
 19   330 ms   358 ms   368 ms  209.85.248.220 
 20   438 ms   450 ms   511 ms  209.85.250.10 
 21  1063 ms     *     1474 ms  209.85.249.23 
 22   495 ms   504 ms   551 ms  216.239.48.115 
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.
 
IPconfig information: 

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Panjwani-PC
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 3:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : 7C-C7-09-C9-DF-37
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Realtek RTL8723B Wireless LAN 802.11n USB 2.0 Network Adapter
   Physical Address. . . . . . . . . : 7C-C7-09-C9-DF-37
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::546:fcec:b49a:9062%3(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.105(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, November 12, 2017 11:32:17 AM
   Lease Expires . . . . . . . . . . : Sunday, November 12, 2017 7:01:53 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 92063497
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-6D-4A-AC-7C-C7-09-C9-DF-37
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:da5d:fa12:20e8:104d:3f57:ff96(Preferred) 
   Link-local IPv6 Address . . . . . : fe80::20e8:104d:3f57:ff96%5(Preferred) 
   Default Gateway . . . . . . . . . : ::
   DHCPv6 IAID . . . . . . . . . . . : 285212672
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-6D-4A-AC-7C-C7-09-C9-DF-37
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{00F742E9-9D69-4B21-A229-3B3AA0176EF4}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
 
*****Test Complete*****! 
05:28 PM
Sun 11/12/2017


Took ten minutes of my precious time, better be worth it. ;)
 

fr0st

SysAdmin
System Administrator
Joined
Jan 28, 2011
Messages
440
Location
Texas
Sorry to tell you but this isnt a problem with RC-RP. It's a problem with your internet.

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

Pinging google.com [74.125.200.102] with 32 bytes of data:
Reply from 74.125.200.102: bytes=32 time=1066ms TTL=39
Reply from 74.125.200.102: bytes=32 time=998ms TTL=39
Reply from 74.125.200.102: bytes=32 time=1165ms TTL=39
Reply from 74.125.200.102: bytes=32 time=1220ms TTL=39
Your ping to other things is ridiculously high and your packet loss is high to other things. It's a problem with your internet, talk to your ISP.
 
Status
Not open for further replies.
Top