Quote:
Originally Posted by Myth Osis
I have experianced this bout 30 sec spikes, but im on a 56k so I kinda just have to deal with it.
|
The LAG seems to be just on the client side.
I base this on the fact that after a while everythig that should have happened inthe time lagging will happen in a matter of 1-2 seconds.
Based on this i tried to continue pushing my skill buttons to see if i could still kill stuff or do things to stay alive ... it worked.
So if you are an ELE spamming flare or somthing ... continue to do so during the lag in the same way as you were used to. If the spike takes a long time .. press buttons like "c" to target e new enemy and start damaging it. etc etc
This is just an example off course. What i am saying is .. stay in the groove of button mashing that you were used to ... it may save your life.
To comment on somebody saying it will mess up the bots ... with what i noticed .. no i think it won't
The problem is the client not getting the much needed updates from the server while the server continues business as usual.
This explains another thing to me ... if it where a serverside problem anet would have an easy time seeing that it was. Being as honest as they have been so far i have no doubt they would have informed us about it.
Conclusion: The problem is communication specific and lies somewhere between the server and the client. It could be that a lot of the traffic is routed over a line with too little bandwidth to handle it all. (combined with extra traffic due to hollidays)
This is one of the reasons, i think, anet want us to do traceroutes and pathpings so they can identify the component most likely to be the cause of the problem.
When they find it .. solving it is another issue because anet is not the owner of those components.
The only thing anet can do on their side is to figure out a way that the server can detect when communication with a client becomes unresponsive. And then decide what to do with that situation.
Shaquira