Slow sword attacks

born2beagator · January 2016

I'm having a strange issue in game. My sword attacks are super slow. Its not stuttering, its not rubberbanding, its just the swing itself is prolonged. My skills are fine. Anyone have any ideas? I've never had this issue before

WhatDoesItMatter · January 2016

I get this too. Sometimes the weapon swings take forever and then pause on the upward swing for a long time. They also sometimes won't queue, which makes doing a power swing very difficult.

I think this problem has been around for a long time. One of the many issues of the game that will never be fixed I suspect.

Tomato · January 2016

The laggggg

Asmodean · January 2016

I'm not completely sure if they're related, but they could be an issue within the overall animation framework. I've noticed similar things throughout various anim types lately.

Various actions seem to be affected by this. (the animations can sometimes go 'slow-mo', or the opposite, and speed up for a second, or two.

Such as;

Attacking animations
PC running animations (running leg anims will speed up drastically for a few secs, or slow down)
Mount running animations (sometimes it gets 'stuck' appearing to be sprinting, when in fact it isn't)

These are just a few other examples of things that might be related to the issue brought up in the OP.

dodgehopper_ESO · January 2016

I get the problem where nothing happens at all sometimes. Bear in mind this is on machines which exceed specs and on 100Meg+ connections. What I mean by nothing happening is that I click a light attack 5 times, and my character just stands there watching butterflies in the distance.

Asmodean · January 2016

@dodgehopper_ESO

It may not be the case, but the first thing that comes to mind is: that could be related to RequestedNumWorkerThreads (if you've tweaked that, in the UserSettings file ). There are a lot of recommendations around online about setting it to 0 to help with frame dips, and stuttering. But, it also increases asset loading times, and threaded processing tasks will take exponentially longer.

Setting it to 0 does actually help majorly with frame drops, and stuttering though. Which I'd imagine is a combination of x86/32-bit binary. Job, and worker thread time slices overlapping. One's trying to get access while the other has it working, and it causing frame drops, and stuttering while switching it up.

#edit: I forgot to mention - I find a nice compromise is to set it to 2, alleviates most of the drops/stutter, and still leaves some threading for speeding up in-game loading.

Hopefully these threading-related tweaks will become unneeded once the x64 patch is released at some stage.