Recent Performance Issues/Strangeness in Cyro

tinythinker · January 2016

I've noticed a few odd things lately, maybe you have too, either similar or different. I've been filing bug reports and I was curious if anyone else has noticed anything. I play on PC-NA, and the occurrences have been in Azura's Star.

1. When I try to open a door sometimes my weapon starts sheathing and unsheathing over and over.
2. When I try to open a door sometimes my character tries to mount then unmount over and over. Other times I might get a "Can't mount in this location" message when clicking on a door.
3. Yesterday I died at a keep that was overrun and rezzed on the other side of the map. Several minutes later I heard siege, battle shouts, armor clanking, etc. I ran outside and there was nothing. I went back in and there was nothing. Then the sound effects stopped.
4. Today after driving off attackers, several of us tried to repair an outer wall. But the game kept saying it had been hit recently. Every so often it would let us get two or three repair kits in, then another "recently received damage" message. But the enemy was gone and there was no enemy siege (unless it was not rendering for us and was silent and invisible). Several minutes into this we all got lit up by fire damage from siege a few times (there was still no enemy siege around). Then more "can't repair" messages. Then the wall jumped to a more advanced state of repair.

Anyone else notice any kind of strange performance issues lately? Or is my copy of the game/connection to the server just *really* messed up?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
New examples I've noticed since the original posting:

5. The spot where a group had sieged a wall and set up some anti-personell equipment still had the hazy glow effect that goes with fire ballistae and firepot trebuchets hanging there in the air even after the group wiped and the wall was repaired. I was going to capture a screenshot but the effects launched forward toward the spot where the breach had been and disappeared.

Robbmrp · January 2016

My game was doing similar things last night in PC-NA-Azura. Others were mentioning that some of their spells that they fired off didn't proc till after they were dead and rezzed in another place. It seems the lag on the server is worse than ever.

Teargrants · January 2016

mike.eso · January 2016

last time I went into azura's, was weeks ago, the transit shrines all disappeared like straight up disappeared, not a single door was usable, couldn't mount, weapon swap, use a skill or anything and no fighting was going on where I was at at least ha needless to say I didn't hang around long on that server and wont ever go back lol but hey the dev's are working on fixing the performance issues might not be anyone left playing by the time the finally do but they're trying.

gw2only1b14_ESO · January 2016

Dunno but can we duplicate this on the Play Test server? if not I suggest we PvP on play test server till issues fixed

frozywozy · January 2016

tinythinker wrote: »

I've noticed a few odd things lately, maybe you have too, either similar or different. I've been filing bug reports and I was curious if anyone else has noticed anything. I play on PC-NA, and the occurrences have been in Azura's Star.

1. When I try to open a door sometimes my weapon starts sheathing and unsheathing over and over.
2. When I try to open a door sometimes my character tries to mount then unmount over and over. Other times I might get a "Can't mount in this location" message when clicking on a door.
3. Yesterday I died at a keep that was overrun and rezzed on the other side of the map. Several minutes later I heard siege, battle shouts, armor clanking, etc. I ran outside and there was nothing. I went back in and there was nothing. Then the sound effects stopped.
4. Today after driving off attackers, several of us tried to repair an outer wall. But the game kept saying it had been hit recently. Every so often it would let us get two or three repair kits in, then another "recently received damage" message. But the enemy was gone and there was no enemy siege (unless it was not rendering for us and was silent and invisible). Several minutes into this we all got lit up by fire damage from siege a few times (there was still no enemy siege around). Then more "can't repair" messages. Then the wall jumped to a more advanced state of repair.

Anyone else notice any kind of strange performance issues lately? Or is my copy of the game/connection to the server just *really* messed up?

Regarding the last bug and the wall repair, it was probably someone sieging from the top of a far away tower. In that scenario, both the visual effect and the sound of the bolt doesn't register.

revonine · January 2016

Point 3 sounds like a ghost story you hear from locations of historic battles. Creepy.

tinythinker · January 2016

frozywozy wrote: »

Regarding the last bug and the wall repair, it was probably someone sieging from the top of a far away tower. In that scenario, both the visual effect and the sound of the bolt doesn't register.

That may be true, even thought the nearby resource had been cleared. It still sounds like a performance issue but one of a different kind. Then again, maybe that isn't what happened.

I went back for a brief time last night and saw a group from my Alliance heading to take a keep. I tagged along in case I could help. The group wiped in the courtyard, but in all of the confusion and ferocious lag I managed to escape and hide. After the wall was repaired and the courtyard cleared out I hopped the wall and made my way out and around the long way to avoid detection.

I ended up passing by the spot where that group had sieged the wall and had set up some anti-personell equipment, and I saw the hazy glow effects that go with fire ballistae and firepot trebuchets hanging there in the air. I was going to capture a screenshot but the effects launched forward toward the spot where the breach had been and disappeared.

Maybe that isn't related to what seemed like delayed siege damage effects earlier in the day, but even if it isn't, it is another example of something odd that isn't working right that I've only recently noticed happening.