Now that I can reliably replicate this issue here is what I can report on it:
It only happens in World of Warcraft.
It also only happens when I click and hold. Thus, things like @cursor macros and @mouseover macros are actually less problematic since they assist in keeping spells functional with less mouse clicks, of course, until I need to reposition my camera or chatacter which is undoubtedly important due to how often it’s done just playing the game, even if I just play casually.
The issue occurs in the direction my mouse was moving while I was clicking and holding in an attempt to replicate this issue. If I right click hold, move my mouse to the bottom left to turn my camera, my cursor (when this issue occurs) WILL end up in the bottom left of the screen. It is very consistent in this way. For this reason, it seems like it’s sort of “releasing” in the background of the game, or something, so the cursor is still active even though it should be stuck and remain until the mouse click is released.
Moving the mouse slowly during has been less likely to trigger than moving the mouse very quickly.
With the raw mouse command enabled, this does not seem to happen during the camera turn - only after I release the mouse, which does make this issue significantly less debilitating.
As I do this on purpose, it happens about every 50 or so click-and-drags. It does not happen with every click-and-drag. It just happens pretty randomly, but consistently occurs again in the future.
The above is all with /script SetCVar(“rawMouseEnable”, 1);
^this enabled.
With it disabled, the cursor seems to instead jump to the center of the screen every time, regardless of direction of movement.
It also seems to be jumping to the center of my screen during the mouse movement while clicked and held, which can cause erratic camera turns when raw mouse is disabled. I am having a hard time replicating this, however. I specifically do not get these with raw mouse enabled, though.
Edit: Tested this all in windowed instead of fullscreen (windowed), now that I can easily test this. It does NOT solve the issue, and continues to jump all the same.