Is there a fix for rubberbanding?

kangkeok · November 2014

Hi, does anyone got an advice to fix this type of lag? its been with me since mod5 patch untill recently it got worse till its unplayable. Usually before mod5, i just restart my modem and it is solved. But this time it wont work. Its been giving me connection time out to account server during login and if i did, i got massive rubberbanding. Sometime its so severe that my char cant move at all despite pressing wasd and after 1 or 2min i was all over the map. This has never been that bad before since i start play this game. If anyone is kind enough to give some advice, i will deeply appreciated. Thanks.

damnataanimus · November 2014

Some rubberbanding is normal, esp with powers like threatening rush or similar. But you say that restarting modem fixed it? Could be a modem issue you need to provide more info, such as a traceroute to cryptic. This thread has a lot more info. http://nw-forum.perfectworld.com/showthread.php?161081-Pro-Tips-on-Diagnosing-Lag-and-Rubberbanding

kangkeok · November 2014

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms D-Link.Home [192.168.1.1]
2 43 ms 43 ms 56 ms 175.137.109.38
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
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.

C:\Windows\system32>

Thanks damnataanimus,, i just did my tracert. Not sure if this is good or bad.

contacting nettest server..
Local IP:
Ping: 333.4 msec
Port: 80: 101 KB/sec 4 KB/sec 107 KB/sec 500
Port: 80: 96 KB/sec 4 KB/sec 102 KB/sec 500
Port: 443: timed out
Port: 443: 110 KB/sec 5 KB/sec 117 KB/sec 500
Port: 7255: 178 KB/sec 7 KB/sec 188 KB/sec 500
Port: 7255: 62 KB/sec 2 KB/sec 66 KB/sec 500
Port: 7003: 65 KB/sec 3 KB/sec 73 KB/sec 500
Port: 7003: 92 KB/sec 4 KB/sec 97 KB/sec 500
Port: 7202: 64 KB/sec 3 KB/sec 68 KB/sec 500
Port: 7202: 29 KB/sec 3 KB/sec 33 KB/sec 500
Port: 7499: 70 KB/sec 3 KB/sec 75 KB/sec 500
Port: 7499: 100 KB/sec 4 KB/sec 106 KB/sec 500
Port: 80: 71 KB/sec 4 KB/sec 79 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit

And my cryptic test

lewstelamon01 · November 2014

Rather bad. Your traceroute is completely timing out after it reaches your ISP gateway...so I'm not really sure what the matter is. Your nettest is also rather bad (400-500 should be what you first and third columns should be getting, ideally, and 20 for the middle).

Is there a fix for rubberbanding?

Comments