OW2: Dual monitor mouse flick bug

Bug: Fullscreen game loses focus with a very quick mouse+click action.

Reproduce:
With two monitors, game set to second monitor, non-primary monitor. Different resolution.
Full screen mode.
Chrome on primary to the right of 2nd.
Really quick mouse flick PLUS mouse CLICK just after, will pull it out of focus SOMETIMES, not every time.
It’s been a bug since day one, but I noticed it’s worse with OW2.
1060 GTX, i7 4770

1 Like

This happens to me also. In full screen mode (not borderless). When I flick really hard, my mouse is on my 2nd monitor and OW2 minimizes.

1 Like

This happens to me as well. Both OW1 & OW2. With 2 different computer builds

1 Like

Same issues happen to me but this time it when it switch to the secondary monitor the drop down resolution settings were from themain monitor. When i swap back to the main monitor the resolution settings are from the secondary. (I can tell this by the differences in refresh rate selections main monitor can use 165 while my secondary can only support 60)

Same issue here. Both borderless and full screen mode. When flicking, mouse slides to the 2nd monitor and OW2 minimizes.

This has been killing me. Are you saying that the problem doesn’t occur if ow runs on the primary display? I’d rather not do that, but I guess I’ll test setting the ow display as primary.

edit: No difference with the ow display set as primary

1 Like

Fix:

  1. Press Escape.
  2. Click anywhere on menu.
  3. That’s it; that’s all the steps.

You can close the menu. You have to do this again after every time you switch away/Alt-Tab from/unfocus Overwatch window.

It’s kinda like how, if you use hover-to-view-images extensions like Imagus/Hover Zoom+, you have to click on a webpage to hover-to-view a .webm nowadays. Which, from what I understand, was a change made to prevent pop-up windows nonconsentually blasting you with .webms.

Happy flicking, my aim-bros! Maybe I’ll see you in my Aim Arena!

1 Like

This actually seems to work!

I don’t know what kind of spaghetti code cause it, since this is the only game I have ever seen do this, but it didn’t happen again when doing this. Wish this wasn’t a thing, but if I said I expect this bug to be ironed out soon I’d be lying: looks like some people had this in OW1 as well.

Thank you for the tip nonetheless.