After logging on after today's maintenance, I spent more time going a few meters over and over again. It took over 15 seconds to get a quest and then it took another 15 seconds for it to show on the npc. Then I tried to start to the quest location and it's back to covering the same ground (movement) again. This happens to some degree after every maintenance, but to today the game is unplayable because of it.
3
Comments
4 28 ms 24 ms 25 ms kra-r2.tpnet.pl [194.204.175.49]
5 50 ms 43 ms 40 ms war-b2-link.telia.net [213.248.89.85]
6 47 ms 46 ms 46 ms ffm-bb2-link.telia.net [213.155.134.212]
7 45 ms 47 ms 46 ms ffm-b5-link.telia.net [62.115.114.91]
8 45 ms 54 ms 47 ms ffm-b4-link.telia.net [62.115.116.17]
9 43 ms 44 ms 44 ms akamai-ic-317154-ffm-b4.c.telia.net [62.115.149.15]
10 44 ms 43 ms 43 ms po110.bs-a.sech-fra.netarch.akamai.com [72.52.48.192]
11 * * * Request timed out.
12 44 ms 56 ms 54 ms ae120.access-a.sech-fra.netarch.akamai.com [72.52.48.197]
13 305 ms 237 ms 313 ms 93.191.173.3
14 140 ms 139 ms 145 ms a209-200-171-102.deploy.static.akamaitechnologies.com [209.200.171.102]
15 149 ms 143 ms 143 ms 198.49.243.237
16 140 ms 142 ms 143 ms patchserver.crypticstudios.com [208.95.184.200]
With all the shard maintenance this game gets each week it still runs like its hosted off a 1980's ZX Spectrum or worse a ZX81.
Ereshkigal - 12k Tiefling SW
Aurora Ravensong - 11.6k Drow CW
e.g. I finished a siege without any lag. Then, I jumped to an "empty" instance for another siege. "Empty" as I did not need invite and when I arrived, there were only 16 players and the Siege was not even started. I had lag right there. I gave up (after 2 minutes) and jumped to another one. There was no lag.
Thanks
Black
Yes, switching instances CAN help, because there might be a couple of hamsters (server hardware) that have less work to do than most. The game is rather obviously run on several hamsters (physical and/or virtual servers), with one hamster controlling several instances. If you are lucky, switching an instance might place you into an instance that is currently controlled by a hamster that is not yet running at full speed.
But if most instances lag (which is the case now), it is likely
- a software problem (introduced by the current patch)
- a hardware problem (not enough hamsters)