2013-07-18, 03:34 AM
Sorry to double post, but seeing as I have a slight update I thought I'd bring some attention to the thread.
I did some experimentation with a packet analysis program called Wireshark, and though I know pretty much nothing about packets and their properties, I did find some information.
1) My outgoing packet length was reasonably larger around the time of the spikes (about 50%. Packets were normally 86, but usually went over 150 around the spikes, but could go as high as 600 rarely).
2) My [Time delta from previous displayed frame:] value was massively larger near the spike times. It is usually just under 0.08 seconds, with noise taking it as high as 0.4, but during the spikes there was always a packet or two that was over 3 seconds, sometimes over 10.
And as a final note, this lag does not exist in the startup menus, or (curiously) the Cash Shop.
I've really searched everywhere for some kind of help on this. Even a VM wouldn't start the game for me (stuck on Loading...). Any thoughts or advice from the more skilled would be massively appreciated.
I did some experimentation with a packet analysis program called Wireshark, and though I know pretty much nothing about packets and their properties, I did find some information.
1) My outgoing packet length was reasonably larger around the time of the spikes (about 50%. Packets were normally 86, but usually went over 150 around the spikes, but could go as high as 600 rarely).
2) My [Time delta from previous displayed frame:] value was massively larger near the spike times. It is usually just under 0.08 seconds, with noise taking it as high as 0.4, but during the spikes there was always a packet or two that was over 3 seconds, sometimes over 10.
And as a final note, this lag does not exist in the startup menus, or (curiously) the Cash Shop.
I've really searched everywhere for some kind of help on this. Even a VM wouldn't start the game for me (stuck on Loading...). Any thoughts or advice from the more skilled would be massively appreciated.

