 | Lag in Grifts and regular gameplay(1) | Category: Technical SupportFebruary-2-2015 4:35 PM PST (10 years ago)  |
| The game is lagging bad for me in Grifts, i hit latency of 2000 plus sometimes, and also in regular areas just killing monsters but it is much higher in the greater rifts, it was working fine all morning, i can browse the internet just fine but when i play Diablo it makes my latency shoot up. i am enclosing my tracert, i dont know if itll show anything as i cannot get the other things to work, like pathping, and the winmrt or whatever it was. Tracing route to 12.129.209.68 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 10 ms 8 ms 9 ms dtr02socomo-tge-0-0-1-0.soco.mo.charter.com [96.34.56.237] 4 * 9 ms * 96-34-76-197.static.unas.sc.charter.com [96.34.76.197] 5 12 ms 10 ms 9 ms 96-34-76-228.static.unas.sc.charter.com [96.34.76.228] 6 22 ms 15 ms 15 ms bbr02atlnga-tge-0-1-0-6.atln.ga.charter.com [96.34.2.170] 7 12 ms 11 ms 28 ms 206.181.23.181 8 21 ms 19 ms 21 ms vb1720.rar3.chicago-il.us.xo.net [216.156.0.177] 9 * 19 ms 19 ms 207.88.14.194.ptr.us.xo.net [207.88.14.194] 10 59 ms * 60 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90] 11 57 ms 52 ms 54 ms cr1.cgcil.ip.att.net [12.122.133.34] 12 * 54 ms 54 ms 12.123.251.21 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. | ||
 | Lag in Grifts and regular gameplay(2) | February-2-2015 4:46 PM PST (10 years ago) |
| alehr, Let's download WinMTR. This tool will run a different style of pathping which will hopefully give us a little bit more information about what might be going on with the connection. 1. Download WinMTR 2. Unzip the WinMTR.zip file to the Desktop. 3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows. 4. Run the WinMTR.exe 5. Type the IP address you want to trace in the "Host" field. You can find the needed IP address in our "Running A Pathping Test" support article, which mentions all of our IPs used for troubleshooting purposes. 6. Click on "Start" and then launch the game. Once you notice the connection issue, play for about 10 more minutes, minimize the game and click on "Stop". 7. Click on "Copy text to clipboard" and paste the results into your next forum reply. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(5) | February-2-2015 5:53 PM PST (10 years ago) |
| alehr, |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 718 | 718 | 0 | 0 | 47 | 1 | | No response from host - 100 | 144 | 0 | 0 | 0 | 0 | 0 | |dtr02socomo-tge-0-0-1-0.soco.mo.charter.com - 30 | 333 | 236 | 9 | 20 | 48 | 25 | | 96-34-76-197.static.unas.sc.charter.com - 20 | 401 | 321 | 12 | 23 | 55 | 36 | | 96-34-76-228.static.unas.sc.charter.com - 23 | 380 | 295 | 10 | 22 | 53 | 20 | |bbr02atlnga-tge-0-1-0-6.atln.ga.charter.com - 21 | 393 | 311 | 10 | 25 | 53 | 27 | | 206.181.23.181 - 22 | 384 | 300 | 10 | 25 | 86 | 24 | As soon as your connection leaves your home network and enters your ISP's local network it starts to experience a significant amount of data loss. This data loss continues into every following hop. It looks like at the time that you were running the WinMTR, your ISP may have been experiencing some issues which were contributing to your lag issue. If the issue persists, you are going to want to contact them to have them look into this further. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(7) | February-3-2015 2:18 PM PST (10 years ago) |
| Eman, |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 6 | 463 | 437 | 0 | 0 | 2 | 0 | | 10.73.168.1 - 6 | 463 | 437 | 0 | 13 | 66 | 7 | | ip68-4-12-9.oc.oc.cox.net - 6 | 463 | 437 | 0 | 12 | 74 | 11 | | ip68-4-11-2.oc.oc.cox.net - 0 | 437 | 437 | 6 | 22 | 78 | 7 | | langbprj01-ae1.rd.la.cox.net - 6 | 462 | 437 | 0 | 14 | 69 | 11 | | xe-9-0-3.edge2.LosAngeles9.Level3.net - 6 | 462 | 437 | 0 | 15 | 88 | 46 | | ae-207-3607.bar2.Tustin1.Level3.net - 6 | 462 | 437 | 0 | 29 | 513 | 11 | | ae-207-3607.bar2.Tustin1.Level3.net - 6 | 454 | 427 | 0 | 27 | 108 | 12 | Your connection is experiencing a constant 6% data loss which starts on the connections first hop. This usually indicates that there may be an issue in your home network. I would first try powercycling the connection and then running another WinMTR. If the data loss is still there, you might want to make sure that all the cabling in your home network is secure, and not damaged. Here's a support article with steps on how to the power cycling: Resetting Network Devices If that doesn't work try flushing the DNS. Let me know what happens. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(13) | February-5-2015 3:28 PM PST (10 years ago) |
| Eman, 1. Was the last WinMTR report that you posted ran when you were experiencing the latency issue? 2. Can you provide the following information about your home network? * Windows Xp, Vista, 7,or 8 (also include if it's a 32 or 64 bit version) * Firewall (McAfee, Norton, ZoneAlarm, etc.) * Network Adapter brand, model, driver date, and driver version number (Steps below) 1. Click Start. 2. Click Control Panel. 3. Double-click on the System icon (in Windows XP, you may need to click Switch to Classic 4. View on the left hand side of the screen). 5. Select the Hardware tab. 6. Click on Device Manager 7. Expand the section labeled Network Adapters. 8. Right-click on your network card and select Properties. 9. Click on the "Driver" tab at the top * Router brand and model # (this should be printed somewhere on the front or back or bottom) * Cable or DSL Modem brand and model #(this should be printed somewhere on the front or back or bottom) * ISP (Internet Service Provider) * Is the connection wired or wireless * Location (City, State) ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(22) | February-8-2015 7:24 PM PST (10 years ago) |
| Eman, |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 651 | 651 | 0 | 0 | 205 | 0 | | 10.73.168.1 - 14 | 755 | 650 | 0 | 19 | 424 | 8 | | ip68-4-12-9.oc.oc.cox.net - 14 | 754 | 650 | 0 | 20 | 333 | 10 | | ip68-4-11-2.oc.oc.cox.net - 14 | 754 | 650 | 0 | 11 | 56 | 6 | | langbprj01-ae1.rd.la.cox.net - 14 | 754 | 650 | 0 | 13 | 42 | 18 | | xe-9-0-3.edge2.LosAngeles9.Level3.net - 14 | 754 | 650 | 0 | 13 | 236 | 14 | | ae-106-3506.bar2.Tustin1.Level3.net - 14 | 750 | 645 | 0 | 40 | 281 | 25 | | ae-106-3506.bar2.Tustin1.Level3.net - 14 | 754 | 650 | 0 | 24 | 345 | 13 | That's odd, the WinMTR that you ran in the day time when you weren't experiencing issues shows a 14% data loss occurring in just about every hop in the connection's path. The previous WinMTR that you ran when you were experiencing issues doesn't show any data loss. Would you be able to connect directly to your modem to see if there is any improvement ? That would bypass the router and rule it out as a possible factor. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(27) | February-9-2015 1:18 PM PST (10 years ago) |
| Degamo, why not admit its your server's fault? many of us had the same problems since that tiny update launch.. i had no issues before patch Because we're not sure what may be causing this. It's not happening to everyone, so we need to figure out what may be the common factor with this issue. If I knew for a fact that the issue was on our end, then I'd have no problem admitting it. I'd even share as much info as I could. Anyway, that's why we're troubleshooting, so we can narrow down the cause of this and have it looked into. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(28) | February-9-2015 2:10 PM PST (10 years ago) |
| Eman, killer e2200 gigabit ethernet controller (ndis 6.30) I've seen issues before with Killer network cards. Systems that use them sometimes have another network card that is built into the motherboard. Can you check if you have that? If you do, try plugging into that port instead of the Killer network port and test again. Let me know. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(30) | February-9-2015 5:32 PM PST (10 years ago) |
| Eman, No problem, let's at least make sure that the killer card is running on the most recent drivers. Here's a link where that can be found: MSI Driver Page That driver seems to have been released towards the end of December. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
| Lag in Grifts and regular gameplay(33) | February-9-2015 7:51 PM PST (10 years ago) |
| Exordium, |------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 168.105.24.1 - 2 | 245 | 242 | 2 | 10 | 131 | 9 | | 128.171.28.20 - 1 | 249 | 247 | 1 | 8 | 130 | 5 | | 128.171.28.40 - 2 | 245 | 242 | 1 | 6 | 85 | 69 | | uhm-kolanut-vl667.uhnet.net - 1 | 249 | 247 | 1 | 5 | 126 | 5 | | xe-0-1-0-74-poha.uhnet.net - 1 | 249 | 247 | 1 | 5 | 128 | 5 | | 74-202-119-9.static.twtelecom.net - 2 | 241 | 237 | 2 | 10 | 290 | 145 | | 64-129-238-190.static.twtelecom.net - 2 | 241 | 237 | 65 | 76 | 460 | 65 | | 4.68.71.137 - 25 | 129 | 97 | 66 | 75 | 460 | 143 | | ae-205-3605.bar2.Tustin1.Level3.net - 2 | 241 | 237 | 69 | 77 | 429 | 70 | | ae-205-3605.bar2.Tustin1.Level3.net - 2 | 241 | 237 | 69 | 75 | 298 | 70 | I'm seeing some data loss which is starting on the very first hop that your connection goes through. There is also a 25% loss showing up in the 4.68.71.137, which is in Level 3's network. Try powercycling your connection and then run another MTR to see if the packet loss gets better. If the issue persists, please start your own thread so that we can assist you individually. Here's a support article with steps on how to power cycle: Resetting Network Devices If that doesn't work try flushing the DNS. Let me know what happens. ______________________________________________________ I'm available Sunday through Thursday from 11AM to 8PM Pacific Time Support Contact Information Got some feedback? | ||
