Shroud Raid Phase 1 30% packet loss

[Kargon]

Kargon wondering if are anymathing can be done about silly 30% packet loss during shroud raid, which cause kargon see everymathing about 30 secomonds after happen. Though voice speech happen in realtime with no lag. kargon not get packet loss every time either, only maybe 1 in 3 times run shroud, and kargon notice loss stay for random amount of time, from 2 portals worth to 14 portals worth. packet loss always clear up after phase 1 over. Kargon also try setting all game settaming as low as possimable or disable if possimable, including engine speed to lowest from troubleshooting tab and evermary setting in graphamics tab.

any idea what causing this? maybe kargon isp? maybe 2gig ram not enough? maybe 23 gig HD space left not enough?

kargon on win xp so are not some silly vista problamem. kargon apprecimiate any ideas on how fix.

Edit: kargon also want mention that kargon framerate stay fine (20-30 as usuamal), just evermabody are telemaporting straight from one portal to next and standing still, dont look like are swinging or casting to kargon.

[sirgog]

Kargon wondering if are anymathing can be done about silly 30% packet loss during shroud raid, which cause kargon see everymathing about 30 secomonds after happen. Though voice speech happen in realtime with no lag. kargon not get packet loss every time either, only maybe 1 in 3 times run shroud, and kargon notice loss stay for random amount of time, from 2 portals worth to 14 portals worth. packet loss always clear up after phase 1 over. Kargon also try setting all game settaming as low as possimable or disable if possimable, including engine speed to lowest from troubleshooting tab and evermary setting in graphamics tab.

any idea what causing this? maybe kargon isp? maybe 2gig ram not enough? maybe 23 gig HD space left not enough?

kargon on win xp so are not some silly vista problamem. kargon apprecimiate any ideas on how fix.

Edit: kargon also want mention that kargon framerate stay fine (20-30 as usuamal), just evermabody are telemaporting straight from one portal to next and standing still, dont look like are swinging or casting to kargon.

Karhamagon have probamalem with silly latamancey caused by hamaving a million discoball and acid fog and trog camaster AOE spells.

I have the same problem sometimes, but less severe.

[Zor_Prime]

Hey Kargon, try going to a game website and downloading some big update and see if you have the same packet loss. Let it run for a while (the entirety of the download) It's weird that you only get this in the Shroud (or is that actually the case?).

[MrCow]

Though voice speech happen in realtime with no lag.

Voice chat is provided by Gamespy, so it wouldn't be part of the DDO connection.

[ArkoHighStar]

A few people are seeing this, it just seems to be related to part 1

[Kargon]

Hey Kargon, try going to a game website and downloading some big update and see if you have the same packet loss. Let it run for a while (the entirety of the download) It's weird that you only get this in the Shroud (or is that actually the case?).

kargon never see this outside part 1 of shroud, including huge downloads (kargon download stuff 10 gigs at time over a week or two, leave on for hours, never see slowdown), and even if very little CC are be used (like only one dancemaball per portamal) can still happen. maybe relatamed to numbamer of buffs or evermabody swinging inside each other charactermermers....

and the packet loss ALWAMAYS goes steadimally up to 30% and sits between 30% and 33%, and once problems go away it steadimally drop back to 0.0%

Kargon never have problamem in phase 2 or on even if all party in one cornermer fighting all 4 bossames at once in phase 2.

[Ringos]

Ringos see lag in Shroud with very littlmul danc...

Dang it Kargon!!

Yeah, I've noticed some issues too in part one.

Funny, but back in Merida after Part 4, I dropped group and was still hearing voice from about 60 seconds prior...and I just thought everyone was ignoring me!

[Grond]

I get the same thing Kargon, on alot of the runs. There have been a few runs that I didn't lag so bad, but I don't know for sure what the problem is. PentiumD 3.2 Ghz, 2 Gig Ram, GeFroce 256Mb card. I tried dropping my graphics setting, turning sound off, nothing seems to help. Then every once in a while I'll get a run that goes smoothly.

[Sambvca]

I've put this up before, but maybe they'll care if Kargon started the thread.

The altar gets attuned but the server is lagging so bad it thinks the trogs are still alive and fighting?


http://i109.photobucket.com/albums/n49/Sambvca/ScreenShot00080.jpg

Part 5 does the same thing.

[Goose]

I get the same exact thing, always on part 1 every time. High packet loss about 30-40%. I tried the same troubleshooting techniques as Kargon and no dice. I have bug reported it also.

[Cowdenicus]

Oh No Kargon, those are the packets with the Tasty Ham in them too. ;)

[Theboz]

Do a tracert

Start>Run-type"CMD" for Dos command window

In the CMD window Type "Tracert gls.ddo.com" without quotes

and post the results here


most of the time Packet loss is from ISP and the route you connection takes to DDO, but yours does seem odd that it only happends in the raid.


Im having a constant packet loss with Comcast(formerly Insight cable) in the .3 to 2% range, sometimes it goes back to zero. but not often lately. but i am receiving this everyday since Xmas and i have had muliple tech working on my connection to no avail.

[Kargon]

Do a tracert

Start>Run-type"CMD" for Dos command window

In the CMD window Type "Tracert gls.ddo.com" without quotes

and post the results here


most of the time Packet loss is from ISP and the route you connection takes to DDO, but yours does seem odd that it only happends in the raid.




Kargon will give that a try when get home.

And kargon favorimite are when peopamul are looting chests while kargon sees a portamal with 95% health still ;)

[Kargon]

Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 48 ms 51 ms 48 ms adsl-69-109-59-254.dsl.irvnca.pacbell.net [69.10
9.59.254]
3 48 ms * 52 ms dist3-vlan60.irvnca.sbcglobal.net [67.114.50.65]

4 48 ms 51 ms 48 ms bb1-g10-0.irvnca.sbcglobal.net [151.164.92.194]

5 52 ms 52 ms 51 ms ex2-p14-0.eqlaca.sbcglobal.net [151.164.191.75]

6 52 ms 52 ms 51 ms gar6.la2ca.ip.att.net [12.122.79.109]
7 122 ms 122 ms 123 ms 12.127.3.198
8 121 ms 123 ms 123 ms tbr2.sl9mo.ip.att.net [12.122.10.13]
9 124 ms 123 ms 122 ms tbr1.sl9mo.ip.att.net [12.122.9.141]
10 124 ms 122 ms 121 ms tbr1.wswdc.ip.att.net [12.122.10.29]
11 128 ms 119 ms 124 ms cr2.wswdc.ip.att.net [12.122.16.5]
12 123 ms 122 ms 121 ms cr2.n54ny.ip.att.net [12.122.3.37]
13 122 ms 124 ms 123 ms cr1.cb1ma.ip.att.net [12.122.31.126]
14 123 ms 123 ms 120 ms tbr1.cb1ma.ip.att.net [12.122.20.138]
15 116 ms 115 ms 115 ms 12.127.5.93
16 120 ms 117 ms 119 ms 12-122-254-14.attens.net [12.122.254.14]
17 121 ms 120 ms 120 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
18 118 ms 123 ms 120 ms 12.130.10.69
19 121 ms 120 ms 120 ms 206.16.13.87

Trace complete.

[Sambvca]

Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:
1 28 ms 24 ms 21 ms 10.9.95.1
2 24 ms 24 ms 26 ms at-1-1-0-1715.CORE-RTR2.BOS.verizon-gni.net [130
.81.9.229]
3 24 ms 23 ms 24 ms so-0-2-0-0.BB-RTR2.BOS.verizon-gni.net [130.81.2
0.86]
4 25 ms 24 ms 26 ms 0.so-2-2-0.XL2.BOS4.ALTER.NET [152.63.16.13]
5 32 ms 34 ms 32 ms 0.so-6-3-0.XL4.NYC4.ALTER.NET [152.63.0.73]
6 33 ms 31 ms 32 ms 0.ge-7-1-0.BR3.NYC4.ALTER.NET [152.63.3.170]
7 33 ms 31 ms 31 ms 192.205.34.49
8 47 ms 47 ms 47 ms tbr1.n54ny.ip.att.net [12.122.105.46]
9 45 ms 49 ms 47 ms cr2.n54ny.ip.att.net [12.122.16.141]
10 49 ms 47 ms 44 ms cr1.cb1ma.ip.att.net [12.122.31.126]
11 49 ms 48 ms 49 ms tbr1.cb1ma.ip.att.net [12.122.20.138]
12 37 ms 37 ms 36 ms 12.127.5.93
13 46 ms 39 ms 44 ms 12-122-254-14.attens.net [12.122.254.14]
14 39 ms 39 ms 39 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.13
0.0.174]
15 39 ms 39 ms 39 ms 12.130.10.69
16 40 ms 42 ms 41 ms 206.16.13.87
Trace complete.

[Theboz]

Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 48 ms 51 ms 48 ms adsl-69-109-59-254.dsl.irvnca.pacbell.net [69.10
9.59.254]
3 48 ms * 52 ms dist3-vlan60.irvnca.sbcglobal.net [67.114.50.65]

4 48 ms 51 ms 48 ms bb1-g10-0.irvnca.sbcglobal.net [151.164.92.194]

5 52 ms 52 ms 51 ms ex2-p14-0.eqlaca.sbcglobal.net [151.164.191.75]

6 52 ms 52 ms 51 ms gar6.la2ca.ip.att.net [12.122.79.109]
7 122 ms 122 ms 123 ms 12.127.3.198
8 121 ms 123 ms 123 ms tbr2.sl9mo.ip.att.net [12.122.10.13]
9 124 ms 123 ms 122 ms tbr1.sl9mo.ip.att.net [12.122.9.141]
10 124 ms 122 ms 121 ms tbr1.wswdc.ip.att.net [12.122.10.29]
11 128 ms 119 ms 124 ms cr2.wswdc.ip.att.net [12.122.16.5]
12 123 ms 122 ms 121 ms cr2.n54ny.ip.att.net [12.122.3.37]
13 122 ms 124 ms 123 ms cr1.cb1ma.ip.att.net [12.122.31.126]
14 123 ms 123 ms 120 ms tbr1.cb1ma.ip.att.net [12.122.20.138]
15 116 ms 115 ms 115 ms 12.127.5.93
16 120 ms 117 ms 119 ms 12-122-254-14.attens.net [12.122.254.14]
17 121 ms 120 ms 120 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
18 118 ms 123 ms 120 ms 12.130.10.69
19 121 ms 120 ms 120 ms 206.16.13.87

Trace complete.


Give your ISP a call, tell them you are having a connection issue and packet loss, DONT tell them its to a game, though.

your tracert shows an * meaning its timing out at sbcglobal.net [67.114.50.65] it and your tracert has alot of high numbers. That could be from congestion or some other problem.

Tell your Isp to run some test on your line and have them do a tracert to your modem.


Kargon take a look at Sambvca's tracert his is normal.

this is what mine looks like, I have been told that mine is good and normal even though my 2nd hop times out

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 11 ms 12 ms 68.85.179.145
4 11 ms 13 ms 15 ms 68.85.176.169
5 15 ms 16 ms 13 ms 12.125.194.14
6 19 ms 23 ms 17 ms 12.125.194.13
7 55 ms 40 ms 40 ms tbr2.cgcil.ip.att.net [12.123.4.230]
8 39 ms 50 ms 38 ms tbr2.cb1ma.ip.att.net [12.122.10.105]
9 38 ms 60 ms 37 ms 12.127.5.97
10 39 ms 43 ms 37 ms 12-122-254-14.attens.net [12.122.254.14]
11 40 ms 39 ms 39 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
12 42 ms 40 ms 39 ms 12.130.10.69
13 39 ms 55 ms 41 ms 206.16.13.87


And by the looks of your Tracert i can tell you must be on the west coast.

[Preylor]

I have the same issues as Kargamagon. It occurs 110% of the time in Shroud pt 1, also at the 2nd to last Co6 with all the mephit spawns. Same deal with the Titan raid when all the warforged spawn in the final room. Seems to be a spawning issue for me.

Here's my Trace Route.

C:\>tracert gls.ddo.com

Tracing route to gls.ddo.com [206.16.13.87]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 27 ms 29 ms 30 ms 70.71.32.1
3 27 ms 29 ms 29 ms rd1bb-ge5-0-0-13.vc.shawcable.net [64.59.159.194
]
4 26 ms 30 ms 29 ms rc1bb-ge6-0-0.vc.shawcable.net [66.163.69.197]
5 29 ms 29 ms 30 ms rc1wt-pos4-0-0.wa.shawcable.net [66.163.76.126]

6 29 ms 29 ms 30 ms te-3-4.car3.Seattle1.Level3.net [4.71.152.25]
7 30 ms 33 ms 30 ms ge-1-0-0-55.gar1.Seattle1.Level3.net [4.68.105.1
37]
8 30 ms 29 ms 29 ms att-level3-oc48.Seattle1.Level3.net [4.68.127.11
0]
9 102 ms 101 ms 102 ms 12.127.6.58
10 104 ms 101 ms 101 ms cr1.st6wa.ip.att.net [12.122.23.145]
11 101 ms 102 ms 101 ms cr1.cgcil.ip.att.net [12.122.31.161]
12 106 ms 108 ms 107 ms tbr2.cgcil.ip.att.net [12.122.17.234]
13 104 ms 101 ms 101 ms tbr2.cb1ma.ip.att.net [12.122.10.105]
14 100 ms 101 ms 101 ms 12.127.5.89
15 104 ms 101 ms 101 ms 12-122-254-14.attens.net [12.122.254.14]
16 107 ms 101 ms 101 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.13
0.0.174]
17 104 ms 101 ms 102 ms 12.130.10.69
18 107 ms 107 ms 102 ms 206.16.13.87

Trace complete.

[samho]

The * was not quite uncommon from the tracert result. If many people ONLY encounter this issue on part 1, and it suddenly get resolved after/before part 1 then I would say something goes wrong on Turbine's code but not the routing issue.

Just a side note if you really think some node from the traceroute result can be the source of problem, try another thing in console box (or CMD if you prefer)
ping XXX.XXX.XXX.XXX -n 100

(where XXX should be the same one you see on the result of tracert, the number behind n define the ping counter, so it can be longer value if you want a longer diagnose, for example 1000.)

If the avg pocket lost rate there was below to 3~5&#37; then I don't think the problem was on the network routing.

[Thrudh]

I see the exact same thing... Packet loss of 30%... 11000 Bps receive, 1000 Bps send... and pretty much ONLY in Part 1.

It's unplayable.

I turn video down to low, mute sounds, Change engine speed to very low... I can get the packet loss to 15%... I'm still pretty worthless in Part 1, although I can help with the portals now somewhat...

This is ONLY a problem in the Shroud... Every other part of the game works fine, with less than 1% packet loss...

Please fix this... You've got hooked on crafting, but I can't play this raid...

Is there anything I can do to lower the information being sent to my computer? I don't care if the mobs and other players look like stick figures, I just want to be able to keep up with them...

And again, it's not like any other lag... My character doesn't get stuck, doesn't spring back... instead, he runs around fine.. If I cast a spell on myself, it takes effect instantly... it just looks like the monsters and the other players are lagging... not me...

[Venar]

Another place it happens is if you speed run Coalescent chamber without killing stuff. The instance quickly become unplayable to some.

[Willeum_Wallace]

This exact same thing happens to me. Only on part 1 of shroud, sometimes in part 2, but mostly part 1. Please someone help us fix this so we can play this raid. It does not happen every time, but, probably 4 out of 5 runs. Starts to lag about a couple portals in, then fades away usually when everyone is shrining and looting the chests. Then the rest of the raid is fine. What would be causing this? Is there anything we can do to lessen, or better yet, stop this lag? If anyone, especially someone from Turbine has an answer, PLEASE, let us know :)

Thanks for the help............

[Harkle]

G'day guys.. i see this thread is a little old but i seem to be having the same problem altho it isn't restricted to any 1 location.. (marketplace, Wilderness area, 6man dungeons)
i dont get any lag at all.. just loss

only been happening over the last 7 days,
here is my trace

Tracing route to gls.ddo.com [74.201.102.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms NB6.home [192.168.1.1]
2 13 ms 14 ms 11 ms lo1.mel-lns4.vic.westnet.com.au [202.173.
3 14 ms 14 ms 15 ms gi3-9.mel-core.vic.westnet.com.au [202.173.
4 13 ms 11 ms 19 ms gi1-24.mel-pipe-bdr1.iinet.net.au [203.215.6.142]
5 28 ms 25 ms 29 ms gi15-1-3.syd-ult-core1.iinet.net.au [203.215.20.12]
6 28 ms 24 ms 24 ms te13-0-0.syd-mas-core1.iinet.net.au [203.215.20.149]
7 179 ms 174 ms 175 ms 34023.sydp06.cu.reach.com [134.159.160.57]
8 184 ms 183 ms 179 ms i-10-0-0.wil-core02.bx.reach.com [202.84.140.102]
9 181 ms 185 ms 184 ms i-1-2.tlot03.bi.reach.com [202.84.251.238]
10 * * * Request timed out.
11 259 ms 259 ms 259 ms cr2-cr1.lax009.internap.net [66.79.146.206]
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 258 ms 258 ms 259 ms acs007-wdc005-844-cr2.wdc005.internap.net [66.79.147.198]
19 260 ms 260 ms 259 ms cr1-cr2.wdc005.internap.net [66.79.146.201]
20 * * * Request timed out.
21 * * * Request timed out.
22 257 ms 254 ms 254 ms nym009-phi004-813-cr2.nym009.internap.net [66.79.147.10]
23 259 ms 259 ms 260 ms bsn006-nym009-9-cr1.bsn006.internap.net [66.79.158.9]
24 248 ms 250 ms 249 ms bsn004-bsn006-792-mpr1.bsn004.internap.net [66.79.145.34]
25 250 ms 249 ms 250 ms border1.te7-1-bbnet1.bsn003.pnap.net [63.251.128.43]
26 249 ms 250 ms 257 ms turbine-6.border1.bsn003.pnap.net [64.95.76.202]
27 249 ms 249 ms 250 ms 74.201.102.154
28 252 ms 255 ms 253 ms gls.ddo.com [74.201.102.13]

Trace complete.

Ive spoken to my isp and they say the time outs are normal, Unused pipelines or some such..

they got me to ping their servers with an extended ping.. ie; "ping westnet.com.au -t"

the results were no loss's at all after pinging for a little over an hour.. (pink floyd made this time go faster)
here is a few lines

Reply from 202.72.148.215: bytes=32 time=87ms TTL=247
Reply from 202.72.148.215: bytes=32 time=85ms TTL=247
Reply from 202.72.148.215: bytes=32 time=85ms TTL=247
Reply from 202.72.148.215: bytes=32 time=86ms TTL=247
Reply from 202.72.148.215: bytes=32 time=85ms TTL=247
Reply from 202.72.148.215: bytes=32 time=85ms TTL=247
Reply from 202.72.148.215: bytes=32 time=92ms TTL=247

This is an intermittent problems, sometimes once in 30mins, other times it can happen within 5 mins of the previous spike