https://bugs.winehq.org/show_bug.cgi?id=49423
--- Comment #8 from Sveinar Søpler cybermax@dexter.no --- (In reply to Bloody Iron from comment #0)
This seems to be reproducible 100% of the time based on my experience and generally everyone else I've asked, or read comments on the topic.
This input lag is so bad it means World of Warcraft should not be played on any version higher than WINE 4.16 until this input lag bug is fixed, as it makes gameplay elements (complex boss fights) nearly impossible.
I cannot really say if i am having the same problem, but since i am an old git, my ADHD reaction time is hugely diminished vs. a 20 year old :) So, this might mean i have an easier time with this...
However, there IS a wee bit of strange latency that i do not like. I cannot put the finger on when this happened, but it might just be around those times (4.16?), and especially i think it has become a wee bit "weirder" after you HAVE to use "capture mouse" option in winecfg to even be able to turn using the mouse (several bugs on this, but it is a feature me thinks). This again, might be related to various "rawinput" patches especially from staging. I think you should use a wine version that have all the needed vulkan extensions enabled to get the most performance out of DXVK, and i kinda think that 4.16 is too old, but will look into this.
Another thing to test to see if it is better/worse is to tweak with wow's input latency settings: /dump GetCVar("SpellQueueWindow") Default is 400 and is mostly way too high unless you have really bad ping. General rule of thumb seems to be ping + 100.. eg with 50ms ping: /console SpellQueueWindow 150 or disable with: /console SpellQueueWindow 0
As i said, i cannot really put a pointy finger at "huge issues" with this when running with wine-5.7->5.9 or Proton, but i play a melee and mostly just disable SpellQueueWindow completely.