When playing with a controller on PC - both through Steam and not - I have to press each skill button twice to get it to actually work. Has been a problem since early 2024, after a patch (don't recall which one). Stupid thing is, I press the button once eg Shadow Cloak, interact with a container, press Shadow Cloak again and then it works.

There's an additional delay too, since I think early this year, with having controller input set to "automatic" - it can be up to a second, depending on what I'm doing, eg just moving, swapping bars etc.
I use the "automatic" setting so that I can easily switch between the controller and KB/M. I know it won't happen if I switch to just controller, but that UI is really awful compared to the PC UI. And the bigger point is that I shouldn't have to; it never used to be a problem.

Rkindaleft wrote: »

There's also the bug where your character gets stuck frozen in the attack animation when you use channeled abilities or heavy attack. I don't know how many times I've used Snipe or jabs in a rotation where my toon has ended up freezing in the animation meaning I have to roll dodge/block in order to to be able to do anything.

I had a similar thing happen like 2 days ago where my character was frozen in the blocking animation but could still attack.

https://www.youtube.com/watch?v=OZf5bQtvwkI

Not just chanelled or cast, it happens on my Explosive Charge too. I can still move but not cast or attack. Roll dodge or block does not fix it as I can't do them, and only an outside force (a stun) will knock me out of the animation.

It has a tendency to happen in Boss Hardmode fights.

Just did a Stone Garden run. Undaunted taunt would not pull the 2nd boss. Could see the key press, could see the skill highlighted when over the target. Would not fire no matter where I stood.

Used my Explosive Charge, requires a target and distance check. No problem getting it to fire.

Not sure if it's related but a few nights ago I was fighting in Cyrodiil when I suddenly noticed most (though not all) of my skills could not be cast and I couldn't block. Break-free still worked (which is amazing in-and-of-itself) but here's the thing: I could breakfree nonstop as much as I wanted, even when I wasn't stunned. It would charge me stam every time too. Dying did not fix the issue so I just had to log out for the night.

I've also noticed since Update 47 that there seems to be a very high frequency of lag-spikes when attacking or being attacked. It feels like macroslicing when it happens and it happens a LOT, even when fighting in instances and overland in an empty zone.

ZOS pays Akamai Technologies for DDoS protection.

This service includes a scalability model, so if DDoS attacks increase the amount of traffic to ESO's services, ZOS would have to pay more to Akamai for them to use more of their resources/system/hardware/tech to manage this traffic, identifying and prioritizing the internet traffic coming from real players, while trying to block the traffic from bad actors doing the DDoS attack.

Scalability means that the amount of money ZOS pays Akamai and the amount of resources Akamai dedicates for ZOS can be changed quickly to accommodate fluctuations in internet traffic to ESO's servers.

So when massive delays and packet loss start occurring due to these fluctuations in traffic to ESO, and they don't get resolved quickly, that's usually when your abilities stop firing even when you cast them, or you try to drink a potion, but it won't work, or your guard drops seemingly for no reason, or you try to loot a dead mob pressing e and then r to loot all, but instead you cast your ultimate because the press e information never made it to the server and the loot menu never opened, so pressing r instead casts your ultimate, and any number of other weird issues occur.

So the possible factors/reasons I could think of for why our connection to Akamai Technologies to the game server has been degrading so much could be:
1) increase in AI and bot traffic on the internet enables an overall increase in DDoS attacks, causing these issues to occur more often
2) ZOS doesn't have the money to pay Akamai to scale their services up during DDoS attacks
3) Akamai Technologies is having their own hardware/tech issues unrelated to DDoS attacks
4) A large number of players returning to the game are acting as a DDoS attack because it's causing too much traffic through Akamai Technologies to the ESO servers

It's likely a combination of all of these factors, as during prime time for PC NA, especially on Saturdays, the delays get so bad that the game becomes unplayable, but in the early hours, around 3am, especially on week days, connection to PC NA is perfect with no delays.

I don't think the issue is game and ESO server logic itself, even if it could always be further optimized.

Either way, whatever is happening, we can only trace it to Akamai Technologies, and as paying customers who care about the future of ESO, we deserve to be kept in the loop on what's going on. ZOS needs to communicate with us..

Thanks to everyone confirming the issue – it really helps to know we’re not alone with this.

For us, it keeps happening again and again. For example, in Kyne’s Aegis HM Lord Falgraven couldn’t be taunted at times.
And just yesterday we had to abandon multiple times Graven Deep trifecta run at the second boss, because neither the tank nor the DDs were able to target him anymore.

Really hoping this gets looked into soon – it makes certain fights practically impossible.

@ZOS_Kevin – is this issue already on your radar, and can we expect a fix in one of the next patches?

And honestly, people are leaving this great game because of bugs like this, which is a real shame.

Roctan wrote: »

Really hoping this gets looked into soon – it makes certain fights practically impossible.

Man, I don't want to be that guy but... the track record for 'looking into' vs 'fixed issue' isn't a good one with this sort of thing. You'd better just get used to it because it's probably going to be here for a few years. Not that you shouldn't complain non-stop, make /feedback reports EVERY time it happens, and generally be a nuisance about it. Otherwise they *will* leave it this way.