Guild Wars 2 Forum

Latency Tuning Experiments

And I was wondering why ever since yesterday I had terrible delays similar with the skill-lag I faced during early 2014 (https://www.reddit.com/r/Guildwars2/comments/1vjnea/delay_while_playing_need_help_for_solution/cetb7v3)

Basically when there’s a zerg (e.g. world bosses), the skill lags by 5s~10s and basically you just stand there and… cast nothing.

December 10th Elementalist changes

in Elementalist

Posted by: Jishinya.4168

Jishinya.4168

Kodiak.3281:
This is all dog chasing it’s own tail.

Our mobility/heals were gutted. Here we are for Round 2 by moving good traits into Master tier so we can’t get the benefit of having two good traits in the Adept/Master slot and instead only get one good trait in a Master slot and something useless in the Adept slot.

OH! But why oh why is there no build diversity!?!

Anet is the root cause of this problem. They nerf our survivability on a class that already suffers survivability issues because we spec into survivability to resolve those survivability issues which only furthers our need to spec into survivability which causes a seemingly endless barrage of nerfs to our survivability.

It’s like they’re incapable of seeing the forest through the trees. One of these days someone over there, probably some brash young intern, will recognize that if they wanted build Diversity all they need to do is raise our hitpoints up and we’ll no longer be forced into survivability paths and we all all cheerfully play builds that we actually want instead of builds we are forced to just to survive.

But, you know, lets take a wrecking ball to the whole existing survivability structure to see if that breaks it up. I’m sure when we’re at thief level survivability but completely and totally lack their burst damage or in combat mobility that people are assured to keep playing the class because….

…uh…

…reasons.

Basically this. One of the main reason that almost everyone specs into water and arcana, is because they we NEED it to survive, not because we loves it. Being the lowest base HP AND light armor is not fun. Elementalist has mobility? Let’s get real here. Everyone knows how other jobs has better mobility AND survivability AND even damages.

Dec. 10th Balance Preview - Updated Nov 6th.

in Guild Wars 2 Discussion

Posted by: Jishinya.4168

Jishinya.4168

An elementalist here:

Strongly disagree on this one – “Water V – Cleansing Wave. Moved to Master tier.”. Ele’s already an squishiest class in the entire game and we hardly could keep up with condi removal.

Also, the right way to “avoid power creep” is to buff up other traits in other elements (fire / air / earth) instead of upping tier of existing traits.

LAG issues NOT client sided.

in Account & Technical Support

Posted by: Jishinya.4168

Jishinya.4168

Xystus.3241:

Jishinya.4168:

Here’s another ping on another of their server, seems worse.

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

C:\Users\User&gt;pathping 64.25.33.64

Tracing route to 64.25.33.64 over a maximum of 30 hops

  0  User-PC.lan [192.168.1.67]
  1  192.168.1.254
  2  58.71.243.229
  3  58.71.243.230
  4  58.71.243.53
  5  58.71.243.49
  6  58.71.244.254
  7  58.71.241.57
  8  58.71.241.82
  9  202.151.241.137
 10  202.151.252.254
 11  xe-5-2-0.edge1.LosAngeles6.Level3.net [4.26.0.121]
 12  vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
 13  ae-72-72.ebr2.LosAngeles1.Level3.net [4.69.137.21]
 14  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 15  ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
 16  ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
 17  4.59.197.34
 18  64.25.32.9
 19  64.25.32.26
 20  64.25.32.82
 21     *        *        *
Computing statistics for 500 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           User-PC.lan [192.168.1.67]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2    2ms    13/ 100 = 13%    13/ 100 = 13%  58.71.243.229
                                0/ 100 =  0%   |
  3    5ms     0/ 100 =  0%     0/ 100 =  0%  58.71.243.230
                                0/ 100 =  0%   |
  4    3ms     1/ 100 =  1%     1/ 100 =  1%  58.71.243.53
                                0/ 100 =  0%   |
  5    5ms     1/ 100 =  1%     1/ 100 =  1%  58.71.243.49
                                0/ 100 =  0%   |
  6    5ms     0/ 100 =  0%     0/ 100 =  0%  58.71.244.254
                                0/ 100 =  0%   |
  7    7ms     0/ 100 =  0%     0/ 100 =  0%  58.71.241.57
                                2/ 100 =  2%   |
  8  ---     100/ 100 =100%    98/ 100 = 98%  58.71.241.82
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%    98/ 100 = 98%  202.151.241.137
                                0/ 100 =  0%   |
 10  214ms     2/ 100 =  2%     0/ 100 =  0%  202.151.252.254
                                1/ 100 =  1%   |
 11  184ms     4/ 100 =  4%     1/ 100 =  1%  xe-5-2-0.edge1.LosAngeles6.Level3.
net [4.26.0.121]
                                0/ 100 =  0%   |
 12  184ms     4/ 100 =  4%     1/ 100 =  1%  vlan70.csw2.LosAngeles1.Level3.net
 [4.69.144.126]
                                0/ 100 =  0%   |
 13  184ms     3/ 100 =  3%     0/ 100 =  0%  ae-72-72.ebr2.LosAngeles1.Level3.n
et [4.69.137.21]
                                0/ 100 =  0%   |
 14  217ms     4/ 100 =  4%     1/ 100 =  1%  ae-3-3.ebr3.Dallas1.Level3.net [4.
69.132.78]
                                0/ 100 =  0%   |
 15  219ms     3/ 100 =  3%     0/ 100 =  0%  ae-63-63.csw1.Dallas1.Level3.net [
4.69.151.133]
                                1/ 100 =  1%   |
 16  216ms     4/ 100 =  4%     0/ 100 =  0%  ae-1-60.edge2.Dallas1.Level3.net [
4.69.145.11]
                                1/ 100 =  1%   |
 17  229ms     5/ 100 =  5%     0/ 100 =  0%  4.59.197.34
                                0/ 100 =  0%   |
 18  230ms     5/ 100 =  5%     0/ 100 =  0%  64.25.32.9
                               95/ 100 = 95%   |
 19  ---     100/ 100 =100%     0/ 100 =  0%  64.25.32.26
                                0/ 100 =  0%   |
 20  ---     100/ 100 =100%     0/ 100 =  0%  64.25.32.82

Trace complete.

C:\Users\User&gt;

What server are you on? While you do have some packet loss pre-ANET/NCSOFT space; it is tolerable.

However, this is not good:

18 230ms 5/ 100 = 5% 0/ 100 = 0% 64.25.32.9
95/ 100 = 95% |
19 —- 100/ 100 =100% 0/ 100 = 0% 64.25.32.26

I would open a trouble ticket with this information as it resides on their address space. The 100% packet loss can be ignored, as they are probably blocking the requests. But up to there, we see that node experiencing 95% loss.

I’m on Sea of Sorrows, US Server. I’m really not sure whether if it’s not ANET’s problem or vice versa. There seems to be a few players having the same problem like I do; but majority that are facing it are having the same symptom (i.e. hard to login, long loading screen, easily getting disconnected during mid-game or even getting disconnected right after completing the loading screen).

Their tickets? Gah, I’ve had bad experiences with them. Had an issue previously and was basically re-routed from one department to another; and finally was told to submit a report from their in-game support system; which up till now, did not solve my initial problem (but that’s out of the context).

LAG issues NOT client sided.

in Account & Technical Support

Posted by: Jishinya.4168

Jishinya.4168

Here’s another ping on another of their server, seems worse.

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

C:\Users\User>pathping 64.25.33.64

Tracing route to 64.25.33.64 over a maximum of 30 hops

  0  User-PC.lan [192.168.1.67]
  1  192.168.1.254
  2  58.71.243.229
  3  58.71.243.230
  4  58.71.243.53
  5  58.71.243.49
  6  58.71.244.254
  7  58.71.241.57
  8  58.71.241.82
  9  202.151.241.137
 10  202.151.252.254
 11  xe-5-2-0.edge1.LosAngeles6.Level3.net [4.26.0.121]
 12  vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
 13  ae-72-72.ebr2.LosAngeles1.Level3.net [4.69.137.21]
 14  ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
 15  ae-63-63.csw1.Dallas1.Level3.net [4.69.151.133]
 16  ae-1-60.edge2.Dallas1.Level3.net [4.69.145.11]
 17  4.59.197.34
 18  64.25.32.9
 19  64.25.32.26
 20  64.25.32.82
 21     *        *        *
Computing statistics for 500 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           User-PC.lan [192.168.1.67]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2    2ms    13/ 100 = 13%    13/ 100 = 13%  58.71.243.229
                                0/ 100 =  0%   |
  3    5ms     0/ 100 =  0%     0/ 100 =  0%  58.71.243.230
                                0/ 100 =  0%   |
  4    3ms     1/ 100 =  1%     1/ 100 =  1%  58.71.243.53
                                0/ 100 =  0%   |
  5    5ms     1/ 100 =  1%     1/ 100 =  1%  58.71.243.49
                                0/ 100 =  0%   |
  6    5ms     0/ 100 =  0%     0/ 100 =  0%  58.71.244.254
                                0/ 100 =  0%   |
  7    7ms     0/ 100 =  0%     0/ 100 =  0%  58.71.241.57
                                2/ 100 =  2%   |
  8  ---     100/ 100 =100%    98/ 100 = 98%  58.71.241.82
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%    98/ 100 = 98%  202.151.241.137
                                0/ 100 =  0%   |
 10  214ms     2/ 100 =  2%     0/ 100 =  0%  202.151.252.254
                                1/ 100 =  1%   |
 11  184ms     4/ 100 =  4%     1/ 100 =  1%  xe-5-2-0.edge1.LosAngeles6.Level3.
net [4.26.0.121]
                                0/ 100 =  0%   |
 12  184ms     4/ 100 =  4%     1/ 100 =  1%  vlan70.csw2.LosAngeles1.Level3.net
 [4.69.144.126]
                                0/ 100 =  0%   |
 13  184ms     3/ 100 =  3%     0/ 100 =  0%  ae-72-72.ebr2.LosAngeles1.Level3.n
et [4.69.137.21]
                                0/ 100 =  0%   |
 14  217ms     4/ 100 =  4%     1/ 100 =  1%  ae-3-3.ebr3.Dallas1.Level3.net [4.
69.132.78]
                                0/ 100 =  0%   |
 15  219ms     3/ 100 =  3%     0/ 100 =  0%  ae-63-63.csw1.Dallas1.Level3.net [
4.69.151.133]
                                1/ 100 =  1%   |
 16  216ms     4/ 100 =  4%     0/ 100 =  0%  ae-1-60.edge2.Dallas1.Level3.net [
4.69.145.11]
                                1/ 100 =  1%   |
 17  229ms     5/ 100 =  5%     0/ 100 =  0%  4.59.197.34
                                0/ 100 =  0%   |
 18  230ms     5/ 100 =  5%     0/ 100 =  0%  64.25.32.9
                               95/ 100 = 95%   |
 19  ---     100/ 100 =100%     0/ 100 =  0%  64.25.32.26
                                0/ 100 =  0%   |
 20  ---     100/ 100 =100%     0/ 100 =  0%  64.25.32.82

Trace complete.

C:\Users\User>

LAG issues NOT client sided.

in Account & Technical Support

Posted by: Jishinya.4168

Jishinya.4168

Facing serious disconnections / delay / login failure issue here. Here’s some pathping for those that are interested.

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

C:\Users\User&gt;pathping 64.25.38.242

Tracing route to 64.25.38.242 over a maximum of 30 hops

  0  User-PC.lan [192.168.1.67]
  1  192.168.1.254
  2  58.71.243.109
  3  58.71.243.110
  4  58.71.243.53
  5  58.71.243.49
  6  58.71.244.254
  7  58.71.241.57
  8  58.71.241.82
  9  202.151.241.137
 10  202.151.252.254
 11     *        *        *
Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           User-PC.lan [192.168.1.67]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2    2ms    12/ 100 = 12%    12/ 100 = 12%  58.71.243.109
                                0/ 100 =  0%   |
  3    3ms     0/ 100 =  0%     0/ 100 =  0%  58.71.243.110
                                0/ 100 =  0%   |
  4    5ms     1/ 100 =  1%     1/ 100 =  1%  58.71.243.53
                                0/ 100 =  0%   |
  5    4ms     0/ 100 =  0%     0/ 100 =  0%  58.71.243.49
                                0/ 100 =  0%   |
  6    5ms     1/ 100 =  1%     1/ 100 =  1%  58.71.244.254
                                0/ 100 =  0%   |
  7   13ms     0/ 100 =  0%     0/ 100 =  0%  58.71.241.57
                               42/ 100 = 42%   |
  8  ---     100/ 100 =100%    58/ 100 = 58%  58.71.241.82
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%    58/ 100 = 58%  202.151.241.137
                                0/ 100 =  0%   |
 10  289ms    42/ 100 = 42%     0/ 100 =  0%  202.151.252.254

Trace complete.

C:\Users\User&gt;pathping 64.25.38.242

Tracing route to 64.25.38.242 over a maximum of 30 hops

  0  User-PC.lan [192.168.1.67]
  1  192.168.1.254
  2  58.71.243.109
  3  58.71.243.110
  4  58.71.243.53
  5  58.71.243.49
  6  58.71.244.254
  7  58.71.241.57
  8  58.71.241.82
  9  202.151.241.137
 10  202.151.252.254
 11     *        *        *
Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           User-PC.lan [192.168.1.67]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2    2ms    12/ 100 = 12%    12/ 100 = 12%  58.71.243.109
                                0/ 100 =  0%   |
  3    3ms     0/ 100 =  0%     0/ 100 =  0%  58.71.243.110
                                0/ 100 =  0%   |
  4    5ms     1/ 100 =  1%     1/ 100 =  1%  58.71.243.53
                                0/ 100 =  0%   |
  5    4ms     0/ 100 =  0%     0/ 100 =  0%  58.71.243.49
                                0/ 100 =  0%   |
  6    5ms     1/ 100 =  1%     1/ 100 =  1%  58.71.244.254
                                0/ 100 =  0%   |
  7   13ms     0/ 100 =  0%     0/ 100 =  0%  58.71.241.57
                               42/ 100 = 42%   |
  8  ---     100/ 100 =100%    58/ 100 = 58%  58.71.241.82
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%    58/ 100 = 58%  202.151.241.137
                                0/ 100 =  0%   |
 10  289ms    42/ 100 = 42%     0/ 100 =  0%  202.151.252.254

Trace complete.

C:\Users\User&gt;

SEA players lagspikes, ISPs with Level3 route

in Account & Technical Support

Posted by: Jishinya.4168

Jishinya.4168

I have the exact same problem. Go anywhere without too much of people will be fine. But any champs / bosses / events, and I’ll be greet with continuous disconnections and it’ll take forever for me to get back online.

This wasn’t happening previously but specifically today, it’s been going on for almost the entire day.

:(

Showing Posts For Jishinya.4168: