Always follow what is true.” — Sentry-skritt Bordekka
GW2 Client Won't Patch Completely
Always follow what is true.” — Sentry-skritt Bordekka
Whats ur ISP & Router ?
personally, every patch i have to close/open the launcher like 10 times, else it drops to 0 kbps and never picks off, sometimes it does. mostly not.
Whats ur ISP & Router ?
personally, every patch i have to close/open the launcher like 10 times, else it drops to 0 kbps and never picks off, sometimes it does. mostly not.
My ISP connection is via 6Mb/sec wide-area wireless through a dish/base station link. I’ve been using it for about 18 months, and aside from occasional issues related to extreme weather or equipment failures, it’s been pretty good.
When I suspect network problems, I run pings just in case, and this is a typical summary of what my pings look like to GuildWars.com, whether the GW2 launcher is running (and exhibiting the patching problem) or not:
Ping statistics for 64.25.40.51:
Packets: Sent = 399, Received = 399, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 139ms, Average = 52ms
If there’s a better address to ping for diagnostic purposes, I’d love to know. The game servers themselves (as indicated by resmon) don’t reply when I ping their IP addresses directly.
My router is a Netgear WNR3500L that I’ve had since 2010 and is the same router through which I installed GW2 in beta and have patched it successfully ever since.
It’s not normal for me to have to restart the client for a patch to complete, and this problem didn’t occur prior to the Season 3 Episode 2 patch.
Always follow what is true.” — Sentry-skritt Bordekka
Sounds like a solid setup.
Here’s the IP’s i got:
64.25.47.109
206.127.146.33 / 206-127-146-33.ncsoft.com (this is probably it, uses most traffic)
206.127.159.108
pings are below 80ms.
it’s probably ANet issue…
Thanks for the IPs and checking this out.
Interestingly, I do get replies from those addresses, though their latency is much higher than what the client reports on the Options panel in-game, which averages around 80ms or so. To wit:
Ping statistics for 206.127.146.33:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 167ms, Average = 157ms
Ping statistics for 64.25.47.109:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 179ms, Average = 158ms
Ping statistics for 206.127.159.108:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 155ms, Maximum = 168ms, Average = 158ms
So I’m not sure that those IPs correspond to what the client is checking when it reports ~80ms.
It’s definitely puzzling that the launcher loads a small amount of patch data each time it’s launched, then fizzles out to 0kB/sec, yet I was able to download enough to log in on patch day, and the fresh install managed to download 5.64GB of data before stopping just shy of being playable.
I sent in a copy of ArenaNet’s GameAdvisor diagnostic output as request by support, and scanned through it for anything obvious, but the file is very verbose, and nothing jumped out at me.
Hopefully the good folks at ArenaNet will put me on the path to a whole and healthy client soon, but as always, if anyone has any ideas, I’m all ears.
Always follow what is true.” — Sentry-skritt Bordekka
…and then I realized ping.exe measures round-trip latency, the client is probably reporting one-way latency, and ~160ms/2 = ~80ms.
So yeah.
Always follow what is true.” — Sentry-skritt Bordekka
Probably a problematic asset server. Open cmd.exe and enter the following command:
nslookup assetcdn.101.ArenaNetworks.com 8.8.8.8
Pick one of the addresses and use it like so:
Gw2.exe -assetsrv 54.230.119.119
You can also try -log to generate a log file of what it’s trying to download.