Originally Posted by
Woodshock
I am usually sitting at a 268 latency, and no atm I am not using quartz.
This may sound daft, but try mashing your keys.
No, seriously.
You see, the WoW server allows you to "queue" your next spell about 0.3 seconds or so before whatever you're casting finishes. This helps limit the otherwise extremely negative effect of latency on caster DPS.
The trouble is that we humans also take some time to "react" to stimulae such as a spell cast finishing. Average reaction time to a visual stimulus is in the region of 200 ms (0.2 seconds).
So if you start casting only when your spell bar finishes - let's assume 300ms latency for simplicity's sake:
Code:
Time / Action
0ms: your spell finishes casting
<--- reaction time --->
+200ms: you react by pushing a button
<--- latency --->
+500ms: the server gets your instruction
So in this scenario every spell is effectively taking 0.5 seconds longer to cast.
Now, if you get Quartz and time your next cast by its latency bar, that changes to:
Code:
Time / Action
-300ms: Quartz cast bar enters red latency area
<--- reaction time --->
-100ms: you react by pushing a button
<--- latency ---> (during which 0ms: your spell finishes casting)
+200ms: the server gets your instruction
So in this scenario you're only getting 0.2 seconds extra per cast.
Now what if, immediately after your spell starts casting, you start mashing the button for the next spell?*
Code:
Time / Action
-300ms: you are already repeatedly pressing the button
<--- latency --->
0ms: your spell finishes casting
0ms: the server gets your instruction and starts casting the next spell
So at this point you've almost eliminated the effect of latency on your DPS. (Obviously there'd be a short delay between button presses but that's harder to model.) (Also note that the client doesn't let you queue spells during the first second of a cast, so you can't accidentally queue the next-but-one spell!)
The upshot is: try to eliminate reaction time and latency by knowing which spell you're going to cast next and repeatedly pressing the button when your cast is in its last 0.5 seconds or so. It sounds stupid but it may well help your situation.
*Edit: I should probably add that constant button mashing is not actually a good idea in most situations because the actual queue mechanics are a bit more complicated than what I've suggested - it's just the easiest way to test if latency is having an effect. Incorrect use of button-mashing can actually add latency to your casts.