Zero spikes for the first time , only the typical delay , but rly performance on playfield improved
Zero spikes for the first time , only the typical delay , but rly performance on playfield improved
Fury:
Etheecx -Necrow R5
Ebedokles -Priest of Agrigento [threw himself into the volcano!]
Teargarden -Sin R8
Teagarden -Ranger R7
Tempgarden - DeaTea R8
Teadealer -ToS R3
Crom:
Ethicx -Demonologist R10
Bedtime -Guardian R5
SponsoredHox R3 delight
*Chaotic gooD*
Players have been shouting for years that the issue had to be hardware related on the server side. Funcom always denied these claims and deflected the problem with fancy talk about game code and how they couldnt fix it because the way the game was coded in the begining it just couldnt handle massive fights.
They also disregarded our feedback on how the fact that the siege crashes started on the exact same day they did the first batch of server merges (the one they merged Wildsoul, Battlescar, Soulstorm and Twilight into Fury), this coincidence alone should be raising some red flags when the first crash hapened. Who doesnt remember sieging before the mentioned merges without a single red bar? I sure do.
Anyway glad you finnaly figured it out (by accident but who cares right lol). If only you listened to your community more often, maybe just maybe we wouldnt have a train wreck of a game in our hands.
PS: I do have to giggle though when i remember Sillirion actually mentioning they were investigating the possibility of players crashing sieges on purpose, that made sence...lol. Priceless.
Last edited by stuntdragon; 21st May 2013 at 03:31.
yep! the second lagless siege in a row - gj!
26.05 siege on Fury. Fort Bein. Keep t2.
NightWatch attack, Black-Steel+IronWill def.
NightWatch win. Ping green, no lags.
11.06 Stonehammer (T3 BK).
IW+BS (attackers) VS WN.
IW wins.