LonePirate wrote: »I find it interesting, and possibly even telling, that no one from ZOS has chimed in on this thread, even just to comment that they are investigating last night's problems.
Or does everyone have confidence that the problems are being researched without any official proclamations?
LonePirate wrote: »I find it interesting, and possibly even telling, that no one from ZOS has chimed in on this thread, even just to comment that they are investigating last night's problems.
Or does everyone have confidence that the problems are being researched without any official proclamations?
Agrippa_Invisus wrote: »Yesterday was still laggy as heck, though not as bad as 9/23.
There were numerous times while trying to retake Arrius from AD that we saw skill and movement lag. Invasion caused several lag ports through walls and enemy NPCs. Many siege pieces were lost to bugging out.
I suspect, strongly, it's the presence of a lot of player characters in one part of the zone that is causing it. Even if they were in the zone already, just being in one area is bringing the lagstorms.
As soon as the giant zergs dispersed instead of being focused in one area, the lag began to abate, but returned when AD were pushed back to Bloodmayne and there was a large AD zerg defending it. Cyrodiil's servers were definitely designed to have its players distributed around the zone.
To emphasize -- I am NOT blaming AD for the lag. It's the sheer number of players in one area causing it -- and any faction doing it would cause the lag. AD was focusing most of its forces in one area due to not wanting to a) give up a chance at Ghartok and, later, b) not let anyone get Mnem. Both of which are completely understable strategies.
WarrioroftheWind_ESO wrote: »I don't get it. People complained that both CR and TB were poplocked at prime time. Queues were backed up so much people clamored for a new 30 day camp. ZOS added said 30-day camp and people are STILL trying to cram all onto TB. I'm having trouble understanding this mentality, especially when there are other servers in need of players. You know what happens when you get matter so dense it collapses upon itself? A black hole. You know what happens when 300+ people cram into one space on one server?
Had is still in need of strong DC and EP. DC probably more than EP because EP's been consistently giving AD hell. All it takes is 15-20 skilled players to get something started. If all everyone's gonna do is gripe and quit, there'll be no one left to do anything. There's options there everyone's just too stubborn to capitalize on them.
Agrippa_Invisus wrote: »With EP on the flags at Roebeck, having just picked Chim off the scroll pedestal... BAM! Right before the crash, the keep was still listed as yellow (we were all watching intently), and the scroll of Ni-Mohk was stored in Bloodmayne.
Waited until the pop was 2 bars across the board last night and didn't have one crash. Not that much lag either compared to what it has been like.
Agrippa_Invisus wrote: »With EP on the flags at Roebeck, having just picked Chim off the scroll pedestal... BAM! Right before the crash, the keep was still listed as yellow (we were all watching intently), and the scroll of Ni-Mohk was stored in Bloodmayne.
Not sure if you guys were booted before us or if we just got the update sooner, but Vokundein was inside on the flags at Roe and the keep did flip EP right before the crash.
Dleatherus wrote: »Waited until the pop was 2 bars across the board last night and didn't have one crash. Not that much lag either compared to what it has been like.
is the answer capping campaign pops when 2 bars are full and keeping the current number of campaigns to achieve more population balanced campaigns and reduce the lag at the same time?
D.
Agrippa_Invisus wrote: »Agrippa_Invisus wrote: »With EP on the flags at Roebeck, having just picked Chim off the scroll pedestal... BAM! Right before the crash, the keep was still listed as yellow (we were all watching intently), and the scroll of Ni-Mohk was stored in Bloodmayne.
Not sure if you guys were booted before us or if we just got the update sooner, but Vokundein was inside on the flags at Roe and the keep did flip EP right before the crash.
Map in game never updated, nor did the usual alerts go out. We saw Frozn had picked up the scroll, started cheering for him in TS, and then curses as we went back to character select.
Agrippa_Invisus wrote: »Agrippa_Invisus wrote: »With EP on the flags at Roebeck, having just picked Chim off the scroll pedestal... BAM! Right before the crash, the keep was still listed as yellow (we were all watching intently), and the scroll of Ni-Mohk was stored in Bloodmayne.
Not sure if you guys were booted before us or if we just got the update sooner, but Vokundein was inside on the flags at Roe and the keep did flip EP right before the crash.
Map in game never updated, nor did the usual alerts go out. We saw Frozn had picked up the scroll, started cheering for him in TS, and then curses as we went back to character select.
Understood. Just saying it did update for us. We were all talking about it in TS and hoping it didn't rollback.
So apparently they really did fix the "keep state" on crashes. Now they just need to figure out the "scroll state" part.
Dleatherus wrote: »Waited until the pop was 2 bars across the board last night and didn't have one crash. Not that much lag either compared to what it has been like.
is the answer capping campaign pops when 2 bars are full and keeping the current number of campaigns to achieve more population balanced campaigns and reduce the lag at the same time?
D.
Rune_Relic wrote: »Dleatherus wrote: »Waited until the pop was 2 bars across the board last night and didn't have one crash. Not that much lag either compared to what it has been like.
is the answer capping campaign pops when 2 bars are full and keeping the current number of campaigns to achieve more population balanced campaigns and reduce the lag at the same time?
D.
Could it be the capping process itself which is causing the issues rather than the population ?
ie bad code used for the capping.
Sallington wrote: »
It COULD be anything as far as we know since there's no communication as to what they think it could be, or how they're working on it.