| Have had lag since launch of 2.1(1) | Category: Technical SupportSeptember-15-2014 5:05 PM PDT (8 years ago) ![]() | |
| As the title states I have been unable to play a 'playable' version of the game for weeks, it's is completely unplayable, thought this might have been addressed but apparently not. Lag spikes mean i can run to the edge of the map can lag out to find myself dead 30 seconds later, this is all if the game stays stable enough for me to spawn into a dungeon before i get dc'd. http://us.battle.net/d3/en/forum/topic/12186888744?page=11#203 http://us.battle.net/d3/en/forum/topic/14277648146#15 http://us.battle.net/d3/en/forum/topic/14277488184?page=3#60 I tried posting in other heavily populated threads but for nothing. As I stated previously it resembles the pre 1.08 version where i can run to the edge of the map, before that patch I had to run of USB stick due to the games poor usage of the HDD. I have moved house so it's understandable that it might be internet connection. It does feel strangely familiar to the HDD issues though. 1 1 ms 1 ms 2 ms router [192.168.1.1] 2 * ms 9 ms 7 ms nexthop.nsw.iinet.net.au [203.215.19.247] 3 * ms 7 ms 6 ms tel-1.syd-mas-bdr2.iinet.net [203.215.18.20] 4 7 ms 7 ms 7 ms po3-100.syd-mas-brd1.on.ii.net [203.215.20.153] 5 22 ms 57 ms 117 ms ae2.syd-mas-core1.on.ii.net [203.215.20.94] 6 7 ms 7 ms 7 ms xe-7-0-10-10.br1.lax1.on.ii.net [150.101.33.100] 7 153 ms 154 ms 155 ms te0-0-0-1.br1.lax1.on.ii.net [203.16.213.69] 8 * ms 155 ms 158 ms sl-st30-la.sprintlink.net [202.16.213.69] 9 156 ms 154 ms 155 ms 144.232.4.129 10 169 ms 168 ms 166 ms 192.205.32.145 11 166 ms 166 ms 190 ms cr2.la2ca.ip.att.net [12.122.129.98] 12 205 ms 162 ms 164 ms gar29.la2ca.ip.att.net [12.122.129.241] 13 162 ms 164 ms 163 ms 12.122.251.190 14 175 ms 175 ms 173 ms mdf001c7613r003-gig-12-1.lax1.attens.net [12.129.193.254] 15 166 ms 163 ms 187 ms 12.129.209.68 1 ms 1 ms 1 ms router [192.168.1.1] * ms * ms 7 ms nexthop.nsw.iinet.net.au [203.215.19.247] 7 ms 6 ms 15 ms tel-1.syd-mas-bdr2.iinet.net.au [203.215.18.20] 24 ms 7 ms 14 ms po3-100.syd-mas-brd1.on.ii.net [203.215.20.153] 46 ms 7 ms 13 ms ae2.syd-mas-core1.on.ii.net [203.215.20.94] * ms 14 ms 7 ms xe-7-0-10-10.br1.lax1.on.ii.net [150.101.33.100] 158 ms 158 ms 154 ms te0-0-0-1.br1.lax1.on.ii.net [203.16.213.69] 156 ms 157 ms 156 ms sl-st30-la.sprintlink.net [202.16.213.69] 166 ms 154 ms 155 ms 144.232.4.129 167 ms 170 ms 170 ms 192.205.32.145 170 ms 169 ms 174 ms cr2.la2ca.ip.att.net [12.122.129.98] * ms * ms * ms Request Timed Out. 166 ms 166 ms 165 ms 12.122.251.190 * ms 165 ms 165 ms mdf001c7613r003-gig-12-1.lax1.attens.net [12.129.193.254] 187 ms 167 ms 192 ms 12.129.209.68 | ||
| Have had lag since launch of 2.1(2) | September-15-2014 5:52 PM PDT (8 years ago) ![]() | |
| troyshaun, Both tracerts that you posted are showing some possible data loss starting in hop 2. If you have a modem that is a separate device from your router, then hop 2 would represent your modem. If your modem and router are one device, then hop 2 is the first hop into your ISP's local network. Can you tell me if you are using a modem and router or a modem that is also a router? 1 1 ms 1 ms 2 ms router [192.168.1.1] 2 * ms 9 ms 7 ms nexthop.nsw.iinet.net.au [203.215.19.247] 3 * ms 7 ms 6 ms tel-1.syd-mas-bdr2.iinet.net [203.215.18.20] 1 ms 1 ms 1 ms router [192.168.1.1] * ms * ms 7 ms nexthop.nsw.iinet.net.au [203.215.19.247] 7 ms 6 ms 15 ms tel-1.syd-mas-bdr2.iinet.net.au [203.215.18.20] 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. If you are not sure what IP address to use, be sure to check out 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? | ||
