have you tryed the setting ON GAME LAUNCH Exit Battle.net Completely .instaed of minimize battle.net or minimize battle.net to the system tray? or (in the Game) fullscreen (window) i— never had this problem so there’s no way i can test this—
Started playing recently and got this issue right away.
Tried everything possible and found no way to fix it after happening neither how to prevent it from happening.
Windows 10, 1080p resolution, second monitor or not doesnt help, removing mouse app does not help, no addons does not help, DPI has been 800 always, no mouse accel set, lock mouse to window does not help.
Once this happens i have to close and reopen the game - imagine doing that mid run.
Hopefully tech team can find what is causing this behavior.
Please re priotize this issue, it’s very annoying, doesn’t seems to be related to OS or a hardware issue.
1 Like
Expect this issue to be in the game for the next 5 years like the guild ui permissions problem they added 5 years ago know about and refuse to fix
If the hardware cursor stuff is popping up, that definitely sounds like an OS or driver issue. There might be some weird interaction going on between the WoW client and the system, but even still, this issue seems to be affecting a very very tiny number of players. Probably some issue with overlays or some other program using hardware acceleration that is preventing the client from keeping true foreground focus. Tons of things have overlays and HWA that you might not expect.
Because all your settings and background programs likely carried over.
10.1 patch didn’t fix it. Still happening.
I was able to fix my mouse issue by using the AdvancedInterfaceOptions addon and changing some mouse CVar’s back to default. The ones I touched were ‘MouseNoRepositioning’ MouseUseLazyRepositioning’ then I did a reload and my issues were gone.
I tested it with Crispylardon above, if those CVar values are currently default then change them to non defaults and then change them back. Worked for him.
1 Like
Edit: Didn’t fix it permanently. Just worked as a game restart. Just got it again.
Same problem. Is there a fix?
Having same issue. Please fix Dragonriding is not fun with this issue.
Cmon Blizz do better
Just wanted to chime in and join the chorus of disgruntles. AFAIK I’ve only experienced this during Season One, 10.0.7. What I don’t want to have to mess around with are even more addons, specifically those that change hidden settings that I may not have a full grasp of what I’m actually doing.
For the record, I always keep my OS and the subsequent drivers updated.
I currently use this setting along with the option of allowing a ten-second count down before the launcher closes. This shouldn’t make a difference anyway as it’s separate from the client itself.
Did running the client as admin happen to make a difference?
I had this problem, changed two things and haven’t noticed it reoccur:
Turn off pointer precision is Windows Mouse Options.
Close the WoW Launcher before logging into WoW.
Hey again,
As an update with 10.1 this bug was confirmed and is being investigated further. Hopefully we will have some good news to share on a fix soon.
Thanks to everyone that has shared their findings and workarounds in this thread.
9 Likes
I like that solution. FFXIV is working fine and has been through content updates, patches and the like since I installed it 3 years ago. 11 days left on the sub and then it’s time to burn this baby down.
I noticed that when the bug triggers, the mouse cursor moves at the left edge of the primary monitor (my secondary monitor is at the left of the primary monitor). Primary monitor is Acer Predator X34 (3440x1440@100Hz) with 125% scaling. Secondary monitor is Acer V287K (3840x2160@60Hz) with 175% scaling.
The only mouse software I’m using is LittleBigMouse (available on github) which is a useful tool to align the mouse cursor between monitors with different DPI. But I doubt this is the culprit since I’ve seen on this thread people with the same bug on a single monitor setup.
how is this not fixed yet guys come on!
Praying this is fixed when the servers come up.
1 Like