Guild Wars 2

Regarding the lag issue several players have been experiencing, Ashley Segovia suggested we should provide specific information on our Tickets. She only explained how to do it on PC. Can anyone here explain how to do this on a MAC?

Here is her post and this is were it is coming from:
https://forum-en.gw2archive.eu/forum/support/tech/Official-response-on-the-Lag-issues-please/first

“Hey guys we’re currently looking into this issue. To help us along with our investigation, could you please provide your location in addition to your ISP and Netdiag reports. To create a net diag report, please follow the steps below:

1. Navigate to your Guild Wars 2 folder.

2. Right-click on “GW2.exe” and select “Create Shortcut.”

3. Right-click on “GW2.exe – Shortcut” and select “Rename.”

4. Rename this file to “Guild Wars 2 Diagnostic.”

5. Right-click on “Guild Wars 2 Diagnostic” and select “Properties.”

6. Locate the “Target” line and add the following to the end “-diag”
Your target line should look like this: “C:\Games\Guild Wars 2\GW2.exe” -diag

7. Click “Ok” to save your changes.

8. Double click “Guild Wars 2 Diagnostic” to start the test.

Once completed, please click “View Results” and save the results to a text file on your desktop. Once saved, please attach that to this thread (be sure to click “More posting & formatting options…” at the bottom).

Thanks everyone!"

We don’t get that option, -diag doesn’t work for us.

Here is a way for us to get some of our connection details:

https://en.support.guildwars2.com/app/answers/detail/a_id/9245/kw/Lag

There are Mac instructions there.

Otherwise, we don’t have a diagnostic feature.

^— I’m confused Kylla I don’t see any mac instructions on the page you posted O_o.

But yeah, Fraco adding that command runs specific Windows programs so yes we could tell you how to add the command, but absolutely nothing would happen, the game would just launch as usual.

If you know someone with a Windows box you could have them create a shortcut for you and drop it in the folder where the .exe is on the Mac. Absolutely no promises that it will actually run with that flag set though but it’s a thought.

You have to click on LAG then it opens and shows Mac instructions.

can someone help me explain why I am getting bad numbers starting at string 6? What’s it all mean?

traceroute to 64.25.38.160 (64.25.38.160), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.071 ms 9.770 ms 10.017 ms
2 10.64.96.1 (10.64.96.1) 21.701 ms 19.829 ms 19.923 ms
3 98.172.172.184 (98.172.172.184) 20.069 ms 19.900 ms 20.247 ms
4 98.172.172.129 (98.172.172.129) 30.357 ms 19.862 ms 22.478 ms
5 68.1.4.133 (68.1.4.133) 47.513 ms 28.666 ms 25.930 ms
6 xe-5-3-0.edge2.washington4.level3.net (4.53.114.33) 54.573 ms
xe-5-0-0.edge2.washington4.level3.net (4.53.114.29) 29.776 ms 29.880 ms
7 vlan90.csw4.washington1.level3.net (4.69.149.254) 73.434 ms
vlan60.csw1.washington1.level3.net (4.69.149.62) 63.708 ms
vlan70.csw2.washington1.level3.net (4.69.149.126) 59.846 ms
8 ae-61-61.ebr1.washington1.level3.net (4.69.134.129) 69.885 ms 67.103 ms
ae-91-91.ebr1.washington1.level3.net (4.69.134.141) 70.468 ms
9 ae-2-2.ebr3.atlanta2.level3.net (4.69.132.85) 69.901 ms 69.508 ms 70.308 ms
10 ae-7-7.ebr3.dallas1.level3.net (4.69.134.21) 70.405 ms 59.869 ms 66.776 ms
11 ae-93-93.csw4.dallas1.level3.net (4.69.151.169) 63.645 ms
ae-63-63.csw1.dallas1.level3.net (4.69.151.133) 70.977 ms
ae-83-83.csw3.dallas1.level3.net (4.69.151.157) 62.671 ms
12 ae-2-70.edge2.dallas1.level3.net (4.69.145.75) 61.312 ms
ae-4-90.edge2.dallas1.level3.net (4.69.145.203) 78.486 ms
ae-1-60.edge2.dallas1.level3.net (4.69.145.11) 69.733 ms
13 4.59.197.34 (4.59.197.34) 59.366 ms 69.736 ms 62.956 ms
14 64.25.32.9 (64.25.32.9) 66.575 ms 61.439 ms 61.825 ms
15 64.25.32.26 (64.25.32.26) 66.323 ms 65.657 ms 62.434 ms
16 64.25.32.82 (64.25.32.82) 67.093 ms 61.305 ms 70.079 ms
17 * * *

These numbers aren’t that bad! But keep in mind, your connection routes through Washington, Atlanta GA, and Texas, these are high population nodes and you are going to see residual latency there. However, it seems your connection goes through multiple ip hops per node, each hop is a potential packet loss hole. Luckily, your numbers are’t that bad, wait until they say 300+ms, then you’ll see wicked lag lol.

Fraco, have you figured out how to find your info to post on a ticket? And has your lag lessened with the recent updates?