Diablo® III

Can't Play The Game.

This is the second time I have had to post this. My latency is CONSTANTLY jumping from red to green. I have done every damn thing I can do. I have connected right to the modem, bought a brand new dual band router, bought a brand new hard drive, bought a new SS drive which is where D3 is. I have updated all drivers. Went from 4g of ram to 8g of ram. When I got the new hard drives all I did was put Win 7 on it and D3 and I am still getting the damn issue. This is on Blizzards end. Not mine.

I called Cox which is my ISP and they sent out a tech to test the connection. Their meter read just fine and I even have a damn booster. Seriously, what is going to take to get some help here? I am not the only person with this issue.
Reply Quote
Here is my tracert because if someone actually does repsond you're going to ask,

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 29 ms 17 ms * 10.4.88.1
3 9 ms 17 ms 30 ms 68.10.10.141
4 7 ms 7 ms 7 ms 172.22.60.114
5 9 ms 8 ms 8 ms 172.22.50.165
6 11 ms 8 ms 9 ms 68.10.8.181
7 * * * Request timed out.
8 21 ms 14 ms 23 ms 209.48.42.61
9 23 ms 56 ms 22 ms 216.156.8.190.ptr.us.xo.net [216.156.8.190]
10 27 ms 27 ms 26 ms 206.111.0.90.ptr.us.xo.net [206.111.0.90]
11 87 ms 86 ms 105 ms cr2.wswdc.ip.att.net [12.122.81.250]
12 115 ms 90 ms 84 ms cr1.cgcil.ip.att.net [12.122.18.21]
13 83 ms 83 ms 91 ms cr2.dvmco.ip.att.net [12.122.31.85]
14 93 ms 95 ms 94 ms cr1.slkut.ip.att.net [12.122.30.25]
15 85 ms 108 ms 86 ms cr2.la2ca.ip.att.net [12.122.30.30]
16 80 ms 81 ms 81 ms gar29.la2ca.ip.att.net [12.122.129.241]
17 95 ms 204 ms 203 ms 12-122-254-238.attens.net [12.122.254.238]
18 102 ms 142 ms 104 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.

And here is my D3 Preferences text

PreferencesVersion "44"
PlayedCutscene0 "13"
PlayedCutscene1 "12"
PlayedCutscene2 "20"
PlayedCutscene3 "140"
DisplayModeFlags "0"
DisplayModeWindowMode "2"
DisplayModeWinLeft "0"
DisplayModeWinTop "0"
DisplayModeWinWidth "1920"
DisplayModeWinHeight "1040"
DisplayModeUIOptWidth "1920"
DisplayModeUIOptHeight "1080"
DisplayModeWidth "1920"
DisplayModeHeight "1080"
DisplayModeRefreshRate "60"
DisplayModeBitDepth "32"
Gamma "1.000000"
MipOffset "0"
ShadowQuality "5"
PhysicsQuality "1"
ClutterQuality "3"
Vsync "0"
Letterbox "0"
Antialiasing "1"
LowFX "0"
LimitForegroundFPS "1"
MaxForegroundFPS "150"
LimitBackgroundFPS "1"
MaxBackgroundFPS "8"
DisableTrilinearFiltering "0"
ColorCorrection "1"
MipBias "0.000000"
ReflectionQuality "0"
TonemapExposure "1.900000"
TonemapContrast "1.500000"
TonemapSaturation "1.000000"
TonemapGain "1.000000"
HardwareClass "4"
PCIVendor "4318"
PCIDevice "4483"
MasterVolume "0.180000"
EffectVolume "0.190000"
MusicVolume "0.800000"
NarrationVolume "0.180000"
AmbientVolume "0.210000"
ChannelsToUse "32"
SoundDriver "0"
SpeakerMode "0"
ReverseSpeakers "0"
QuestSubtitlesEnabled "0"
CinematicsSubtitlesEnabled "0"
MuteSound "0"
MuteEffects "0"
MuteAmbient "0"
MuteVoice "0"
MuteMusic "1"
Reply Quote
I have done the same thing mate and it's at Blizz server end. No wonder people are leaving this game when they can't get stuff like this right.
Reply Quote
I've downloaded battle ping to see if it helps but it doesn't. This is definitely on Blizzards end. I am sure they won't respond here though. Marvel Heroes really can't get here fast enough.
Reply Quote
Exact same with me for the last 2 days, started yesterday at about about 2:00pm (Australia Gold Coast) was fine when i woke up at about 9am then.....2:00pm....here it is again. I cannot play my usual (HC) with a 1-2 second delay permanently, its not even spiking just always red ping.
Edited by Alvis#6948 on 3/1/2013 8:58 PM PST
Reply Quote
I hope you realize that, out of everything you said, the only relevant parts were you contacting your ISP and the trace route.

All the other mumbo jumbo about 8gb ram, d3 preferences file, and whatnot, are useless. But hey, why don't install a couple other windows versions, and also buy a Mac to see if your lag reduces?

Also reducing your monitor's brightness might help with your lag. Make sure you have speakers turned off too.
Reply Quote
I hope you realize that, out of everything you said, the only relevant parts were you contacting your ISP and the trace route.

All the other mumbo jumbo about 8gb ram, d3 preferences file, and whatnot, are useless. But hey, why don't install a couple other windows versions, and also buy a Mac to see if your lag reduces?

Also reducing your monitor's brightness might help with your lag. Make sure you have speakers turned off too.


you're a jerk, aren't you ?
Reply Quote
I hope you realize that, out of everything you said, the only relevant parts were you contacting your ISP and the trace route.

All the other mumbo jumbo about 8gb ram, d3 preferences file, and whatnot, are useless. But hey, why don't install a couple other windows versions, and also buy a Mac to see if your lag reduces?

Also reducing your monitor's brightness might help with your lag. Make sure you have speakers turned off too.


You're a moron. Bad Ram can cause memory dumps and cause latency. Bad hard drives can cause latency. Look at other threads, the tech support people ask for d3 preferences all the time because sometimes the preferences cause performance issues. There have been plenty of times on this forum they talk about over-heating issues or hardware failure issues. There have also been known issues with sound cards causing performance issues. There is also a difference between Lag and latency spikes, but hey, keep acting like you know what you're talking about.
Reply Quote
Here's an other tracert I caught as the latency spiked to red, then yellow and then back to green.

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 7 ms 8 ms * 10.4.88.1
3 8 ms 9 ms 7 ms 68.10.10.141
4 * 9 ms 17 ms 172.22.60.114
5 13 ms 9 ms 9 ms 172.22.50.165
6 9 ms 9 ms 9 ms 68.10.8.181
7 17 ms * 50 ms 68.1.4.139
8 15 ms 15 ms 15 ms 209.48.42.61
9 14 ms 13 ms 14 ms 216.156.8.190.ptr.us.xo.net [216.156.8.190]
10 16 ms 15 ms 18 ms 206.111.0.90.ptr.us.xo.net [206.111.0.90]
11 83 ms 82 ms 85 ms cr2.wswdc.ip.att.net [12.122.81.250]
12 82 ms 83 ms 83 ms cr1.cgcil.ip.att.net [12.122.18.21]
13 92 ms 82 ms 83 ms cr2.dvmco.ip.att.net [12.122.31.85]
14 83 ms 83 ms 79 ms cr1.slkut.ip.att.net [12.122.30.25]
15 82 ms 83 ms 86 ms cr2.la2ca.ip.att.net [12.122.30.30]
16 81 ms 81 ms 81 ms gar29.la2ca.ip.att.net [12.122.129.241]
17 89 ms 89 ms 81 ms 12-122-254-234.attens.net [12.122.254.234]
18 81 ms 81 ms 81 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
Reply Quote
Alone...there is some packet loss very early on in your connection. Try to reset your connection.
Reply Quote
It seems to be happening in Act 3 for some reason. I have a few hiccups in Act 1 and 2 but in Act 3 the game freezes and it boots me out of the game. I just restarted everything to see if it happens again. It is does I'll post another tracert.

Edit
===

This ONLY happens playing D3. WoW, and PoE are working perfectly fine with no problems.
Edited by Alone1216#1508 on 3/2/2013 11:55 AM PST
Reply Quote
Act 1 is fine. Problems only happen during Act 3.

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 9 ms 7 ms 8 ms 10.4.88.1
3 8 ms 7 ms 15 ms 68.10.10.141
4 8 ms 8 ms * 172.22.60.114
5 10 ms 9 ms 10 ms 172.22.50.165
6 9 ms 9 ms 10 ms 68.10.8.181
7 * * * Request timed out.
8 35 ms 23 ms 23 ms 209.48.42.61
9 19 ms 25 ms 25 ms 216.156.8.190.ptr.us.xo.net [216.156.8.190]
10 * 17 ms 16 ms 206.111.0.90.ptr.us.xo.net [206.111.0.90]
11 87 ms 86 ms 83 ms cr2.wswdc.ip.att.net [12.122.81.250]
12 82 ms 85 ms 85 ms cr1.cgcil.ip.att.net [12.122.18.21]
13 81 ms 84 ms 82 ms cr2.dvmco.ip.att.net [12.122.31.85]
14 84 ms 83 ms 85 ms cr1.slkut.ip.att.net [12.122.30.25]
15 86 ms 83 ms 82 ms cr2.la2ca.ip.att.net [12.122.30.30]
16 83 ms 99 ms 82 ms gar29.la2ca.ip.att.net [12.122.129.241]
17 82 ms 82 ms 81 ms 12.122.251.190
18 122 ms 81 ms 82 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
Reply Quote
Been disconnected 6 times today. I am going to reply to this thread every single day until there is a real answer, This is the only game that does this. No other game I play does this. Nothing on my PS3 or Xbox has issues like D3.
Reply Quote
Make it number 7. This is getting absolutely ridiculous.
Reply Quote
Run a pathping. You are still getting early packet loss.

I also suspect you may be suffering the AT&T backbone issue that is going on right now, as well. A pathping will show what is up.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]