Scramble Scrub
Osmon Surveillance Caldari State
240
|
Posted - 2013.05.21 02:00:00 -
[1] - Quote
CCP Nullarbor wrote:Snaps Tremor wrote:Malkai Inos wrote:CCP Nullarbor wrote:This is beyond awful and even worse that it is affecting people playing planetary conquest on the opening week.
We have teams in multiple studios working on this right now, it is the number one priority for the people involved. Expect to see some more details about getting it fixed this week. I am genuinely curious as to what exacly is the cause of this. Devblog perhaps? I imagine server location plays a part. With corp battles there was a tendency for (globally) local corps to play each other, and the battles were so sparse that general 'not fit for purpose' issues like this might have flown under the radar. Now, with PC, your corp's real world region is irrelevant, so there will be many more cases of Euro teams facing off against US teams, and a good few where multi-national corps field whoever they have at the time, leading to players from potentially the whole globe all descending on the same regional server. In this situation, how can it choose an optimal server for everyone? Tritan is mostly US players and I'm in the UK, and the video reminds me of games I had back in Chromosome when I was dragged into a server that was a bad match for my location. No the issue shown in this video is not server related, network latency or packet loss manifests itself in different ways. This is very clearly a client performance issue and we are working on some changes to fix it. It is a client problem. Right now, the only way to fix the issue is to have everyone reset their PS3's before the battles starts, and to NOT jump into another instant battle after the reset, and before the PC battle start time. It has a success rating of 80% because it'll still happens even after the reset, but not as frequent.
Also, this lag seems to only happen on skim junction (from my experience at-least.) So have your guys look at that map. Last time there were complaints about the issue, there was something that was said about this particular map was a memory leak or something. There were never any notes that I saw that told us that the problem was actually fixed.
on a side note, I said "that" a lot. |